Note: Likely to be broken out into multiple stories

Context

With the runtime and build-time resources reclaimed, there remains a need to fully complete the logical and user-facing decommission of the Red Hat Marketplace integration. While the service no longer runs, references, data pathways, and API-facing options still exist. This creates potential confusion and maintenance drag.

Open Questions & Work to Complete

1. User-Facing Data Partitioning

• • Is there user-facing data partitioned by billing provider (including RHM) that needs to be preserved for historical reasons?
  • Can we safely remove RHM as an accepted API parameter for billing provider?

1. Code Removal

• • Scope and implement removal of remaining RHM-specific code, tests, and pipeline configs once validated that no customer dependencies exist.

Ideal Retirement Plan

• Remove RHM as an option from any user-facing API params.
• Fully delete code, tests, and pipeline remnants for RHM.
• Ensure documentation reflects removal of RHM as a supported provider.