Major - The Templatized-Policy-Feature is a powerful feature to lookup Managed-Cluster specific values. It would be great if we can combine it with setting vars when calling Ansible as you see https://github.com/ch-stark/demo-subscription-gitops/blob/master/ansible/pacman/prehook/create_snow_ticket.yaml#L10
- * We could even send the encrypted kubeconfig this way (with from-secret function)
Why is this important?
* would be a win-win situation for both features
Scenarios
- should be used in all integration scenarios. We can also use TemplatizedPolicies on the Hub, we just need the name of the Managed-Cluster
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>
