-
Story
-
Resolution: Done
-
Undefined
-
None
-
3
-
False
-
None
-
False
-
-
ACM-33 - Multi-cluster Governance, Risk & Compliance (GRC)
-
-
-
GRC Sprint 2024-10, GRC Sprint 2024-11
-
No
Value Statement
There are cases where an update to an object is required but the fields are immutable. It is desirable in this case to delete the object and create it again. This should be opt-in.
Definition of Done for Engineering Story Owner (Checklist)
- Each object template has an option of `recreateOption` that can be `None`, `IfRequired`, and `Always`. The default is `None`.
- The policy generator should support this new field as well.
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_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.
- is documented by
-
ACM-11956 Document the ConfigurationPolicy recreateOption field
- Closed