-
Story
-
Resolution: Done
-
Undefined
-
None
-
2
-
False
-
None
-
False
-
-
ACM-8995 - [RFE] Add setting name on ConfigurationPolicy in PolicyGenerator
-
-
-
GRC Sprint 2024-13, GRC Sprint 2024-14, GRC Sprint 2024-15
-
No
When creating a policy with multiple manifests and `consolidateManfifest: false` the generated ConfigurationPolicies are names after the Policy with an index appended.
This causes issues when attempting to use extraDependencies such as below. Adding an additional manifest will change the index causing the existing dependencies to be incorrect.
Allowing setting the name would also make it easier to identify in the UI when reviewing a policy.
- name: acs-operator remediationAction: enforce policySets: - acs-operator-hub - acs-operator-managed manifests: - path: ns-rhacs-operator.yml - path: ns-stackrox.yml - path: operatorgroup.yml extraDependencies: - name: acs-operator kind: ConfigurationPolicy compliance: "Compliant" - path: subscription.yml extraDependencies: - name: acs-operator kind: ConfigurationPolicy compliance: "Compliant" - path: health/operator/operator-status.yml remediationAction: inform extraDependencies: - name: acs-operator3 kind: ConfigurationPolicy compliance: "Compliant" - name: acs-operator4 kind: ConfigurationPolicy compliance: "Compliant"
- is documented by
-
ACM-14394 Document missing fields in the Policy Generator
-
- Closed
-
- mentioned on
