Details
-
Epic
-
Resolution: Done
-
Critical
-
None
-
ACM Configurable, automatic reconciliation when syncing Secrets and other resources via templating
-
False
-
None
-
False
-
To Do
-
ACM-1215 - ACM Advanced features in Templatized Policies
-
-
0
-
0%
Description
Epic Goal
- Let's assume you store a Secret on the Hub and reference this via fromSecret-function.
What happens if Secret has been updated? We need automatic propagation of this
secret to the client
At the moment manual and documented workaround is necessary:
policy.open-cluster-management.io/trigger-update
we need some mechanism that says "recheck this every X seconds"
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>
