Problem Statement

Cu has a content-view that include RHEL 9 BaseOS, Appstream, RHEL 9 EUS-BASeOS, RHEL 9 EUS-BASeOS, few custom repos.
Cu uses an activation key that can control the enable and disable process of the repositories on the client but the client can manually enable/disable repo from the client side as well.
Cu doesn't want to change the content-view , and wants the satellite to control this enable/disable process(using the Activation key, Host group), the client should have no control of this process.

The client should not be allowed to enable repositories manually using the 'subscription-manager repos --enable=reponame' command or disable it.

User Experience & Workflow

N/A

Requirements

Cu doesn't want to change or remove unwanted repos but at the same time, it can be controlled by the activation key, not by the client.

Business Impact