-
Story
-
Resolution: Unresolved
-
Normal
-
None
Value Statement
As a user I need to easily tell what component a status indicator belongs to in the MCE status.
Definition of Done for Engineering Story Owner (Checklist)
- Status entries are grouped by component, so a single component may be monitoring various resources of different kinds
- When all resources are in their desired state the status is simple and clear
- Component status reflects all issues within the component and can easily be distinguished amongst the other components
- Status components are populated at the start of reconciliation based on the MCE component spec
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.