-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
2
-
False
-
None
-
False
-
-
-
-
GRC Sprint 2023-17, GRC Sprint 2023-19, GRC Sprint 2023-23, GRC Sprint 2024-05
-
No
Value Statement
As an ACM policy user, I need a way to track the rollout status of a policy using kubectl.
As an ACM policy user, I want to know why my rollout failed (i.e. root policy overall rollout status message).
Definition of Done for Engineering Story Owner (Checklist)
- A status.rolloutStatus field is available for root and replicated policies
- A root policy has a rolloutStatus field per cluster.
- This does not include setting the values. They will be null for now.
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.