Epic Goal

Ensure consistency in approval settings between MCE and MCH subscriptions to streamline operations for ACM and MCE operators.

Why is this important?

Maintaining consistency in approval settings simplifies the management process for operators, reduces the likelihood of errors, and enhances user experience by aligning expectations across platforms.

In our current set up it is possible for a customer to have selected manual update for their ACM subscription and be surprised that this election is not percolated through the MCE. It MCE is set as automatic is possible for it to update when a new z-stream is released which may be surprising to the customer. While they are technically able to set MCE update policies through annotation this is not well known or publicized

Scenarios

1. When a user opts for a manual approval process in ACM, the corresponding MCE subscription should inherit this setting automatically.
2. Users who prefer manual approval for MCH subscriptions are likely to desire the same for MCE subscriptions.
3. Anticipated customer requests for a feature to set MCE approval to "manual" necessitate preemptive action to streamline this process.

Acceptance Criteria

1. MCE subscriptions inherit approval settings from corresponding MCH subscriptions by default.
2. When a user opts for manual approval in ACM, the corresponding MCE subscription is automatically set to manual approval mode.
3. Support for existing customers who have manually configured MCE approval settings is provided during the transition period.

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.