-
Story
-
Resolution: Unresolved
-
Undefined
-
ACM 2.13.0
-
2
-
False
-
None
-
False
-
-
ACM-13020 - [RFE] add spec.versions support in Policy template
-
-
-
GRC Sprint 2024-22
-
None
Value Statement
As an OperatorPolicy user, I'd like to have the spec.versions field by dynamic with managed cluster templates. The current workaround is to use hub templates.
Definition of Done for Engineering Story Owner (Checklist)
- The spec.versions field can take template values.
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- is documented by
-
ACM-15639 Document templating in the OperatorPolicy spec.versions field
- Backlog