-
Epic
-
Resolution: Done
-
Critical
-
ACM 2.8.0
-
ACM Creating a Controller for GitopsOperator Integration which uses a Pull Model (Phase 1)
-
False
-
None
-
False
-
Green
-
To Do
-
ACM-1234 - ACM Creating a Controller for GitopsOperator Integration which uses a Pull Model
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- ACM Creating a Controller for GitopsOperator Integration which uses a Pull Model (Phase 1)
- We start with Designing (see also parent feature for more details)
Why is this important?
- Customers are asking often for Pull-Model
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>
ACM Epic Done Checklist
See presentation and details.
Update with "Y" if Epic meets the requirement, "N" if it does not, or "N/A" if not applicable.
- Y FIPS Readiness
- Y Works in Disconnected
- Y Global Proxy Support
- Y Installable to Infrastructure Nodes
- Y No impacts to Performance and Scalability
- Y Backup and Restorable
- is cloned by
-
ACM-6168 ACM Creating a Controller for GitopsOperator Integration which uses a Pull Model ( (Phase 2)
- Closed