-
Epic
-
Resolution: Done
-
Critical
-
None
Epic Goal
- See: https://bugzilla.redhat.com/show_bug.cgi?id=1988381
- This is best workaround so far, we will maybe set a label by our controller in the future:
https://access.redhat.com/solutions/6306451
we can just inject some annotation by our controller to indicate the object is touched by policy - This epic covers a short-term solution which might be a script
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>