-
Epic
-
Resolution: Done
-
Critical
-
None
-
Option to have the managed resource automatically deleted, if noncompliant, before applying the new definition
-
False
-
None
-
False
-
Not Selected
-
To Do
-
ACM-33 - Multi-cluster Governance, Risk & Compliance (GRC)
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
In the future it would be useful to have the option to have the managed resource automatically deleted, if noncompliant, before applying the new definition. Maybe a new flag option on the object template, in addition to complianceType, or a new complianceType option like 'musthavewithdelete'. This would eliminate the need for a duplicate mustnothave definition and/or manual intervention to delete resources on the cluster.
This is related to ACM-7639
Scenarios
Acceptance Criteria
Dependencies (internal and external)
Previous Work (Optional):
Open questions:
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
