-
Epic
-
Resolution: Duplicate
-
Major
-
None
-
None
Epic Goal
- While this feature has already been implemented in ACM 2.6 we want to enhance it.
- one possibilty is to have an option of foreground/background deletion policy
similar to what ArgoCD provides when deleting resources.
Why is this important?
- …
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
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>
- clones
-
ACM-1007 ACM After deleting a policy the changes/objects created/modified by the policy are still on the target cluster
- Closed