Feature Overview

MCE subscription should inherit the approval setting from the MCH subscription.

Goals

Goal is to maintain consistency across both the ACM and MCE operators

(Optional) Use Cases

Users that do not want an automatic upgrade:

• Users that do not want an automatic upgrade usually opt for a manual approval process with ACM
• There is a high probability that the same set of users will want the manual approval for MCE too.
• As of now the only way of doing this is manually adding the annotation in the MCH to make the MCE subscription approval manual.
• I have seen support cases where customers have raised a query on how to put the MCE approval to "manual". It is inevitable that a customer is going to request for this feature at some point.

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 10/8/25:

Summary of the Work:
What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."

Key Areas to Verify:

1. What functionality should QE focus on? List what was tested or what is most important to validate.
2. Ensure the new validation messages appear for required fields
3. Confirm the workflow still completes as expected after validation fixes
4. Any edge cases or high-risk areas touched by the change

Fix or Feature Availability:
When will this be available in a build?
Code merged on: YYYY-MM-DD
Expected downstream build tag (if known): example-build-tag
(Optional) Related PR(s): Link