-
Story
-
Resolution: Unresolved
-
Normal
-
MCE 2.7.0
-
None
Value Statement
By enabling users to override environment variables in individual sub-components of MCH, we provide greater flexibility and customization, allowing for more tailored configurations that align with specific needs and supported variables for each resource.
Definition of Done for Engineering Story Owner (Checklist)
- [ ] Users can successfully override environment variables in individual MCH sub-components.
- [ ] Environment variables that are set within MCH override is passed to the component's deployment resource.
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.
- clones
-
ACM-12765 As an MCH developer, I want to enhance the MCH CRD to allow for environment variable overrides for the sub-components
-
- Code Review
-