-
Story
-
Resolution: Done
-
Major
-
ACM 2.11.0, MCE 2.6.0
-
3
-
False
-
None
-
False
-
-
-
-
Installer Sprint 2024-30, Installer Sprint 2024-31, Installer Sprint 2024-32
-
No
Value Statement
To ensure we accurately specify the requirements from other squads for the customizable deployment sizes configuration, we will develop a prototype. This prototype will provide insight into the optimal structure of the configuration and ensure it is readily consumable by our automation processes.
Definition of Done for Engineering Story Owner (Checklist)
- [x] Mocked sizes.yaml is created.
- [x] Mocked sizes.yaml support different size configuration: Small, Medium, Large, and ExtraLarge.
- [x] Bundle automation is able to generate charts with mocked deployment sizes.
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.
- clones
-
ACM-10619 As an MCH/MCE developer, I want to enhance the bundle-automation script to support hubSize configuration
-
- Closed
-