Epic Goal

In the current ACM environment, users are unable to add additional environment variables to deployed resources if they are being maintained by the MCH operator. This is caused by MCH rendering and applying the component based upon a template that is formatted as a helm chart during runtime; therefore, any changes made to the deployed resource would be reverted back in favor of the desired template. This feature would allow for us to extend the MCH CRD to include a new field within the spec.overrides.component section for envOverrides for the sub-component. By allowing the components to have envOverrides, this will provide further customization for the user to maintain their resources.

Why is this important?

Users will now be able to configure environment variables for deployments for further customization.

Scenarios

• User A wants to configure a deployment to create a targetNamespace with a custom value.

Acceptance Criteria

• [ ] Users are able to define environment variables at the sub-component level in their MCH CR instance.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.