-
Epic
-
Resolution: Obsolete
-
Major
-
None
-
None
-
ACM GRC Provide a Way to Push Changes to Git
-
False
-
False
-
To Do
-
ACM-33 - Multi-cluster Governance, Risk & Compliance (GRC)
Epic Goal
- When you create Policies and make changes those changes should be pushed to git
- We need to check that this feature get discussed with other product-areas of RHACM/OPP
- see also: https://next.redhat.com/project/gitops-primer/
Why is this important?
- better User experience
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>
