Epic Goal

Announce the deprecation of oc adm release mirror to current users.

Why is this important?

Removing the command will reduce the number of use-facing commands that need to be documented and maintained. oc-mirror provides a more comprehensive experience, including mirroring OLM catalogs and Sigstore signatures and other functionality that is necessary in most OpenShift deployments.

Having the command announce its own deprecation will increase the odds that users hear about the coming removal in time to calmly migrate to alternatives like oc-mirror.

Scenarios

As a user calling oc adm release mirror ..., I receive a warning to stderr about the deprecation that alerts me to my need to begin migration planning.

Dependencies

We need a clear call from Product Management on when to deprecate and when to remove, because telling folks one thing on stderr and then having something else happen instead creates unnecessary user confusion.

Contributing Teams

• Development - OTA
• Documentation - OTA
• QE - OTA
• PX - OTA
• Others -

Acceptance Criteria

Run oc adm release mirror ... and confirm actionable stderr deprecation complaints.

Drawbacks or Risk

Change is hard, and continuing to invest in parallel tooling would allow existing users to continue with existing approaches. But it would also extend maintenance burden, bug-surface, and confusion for new users trying to decide which of the parallel approaches they should take.

Done - Checklist

• CI Testing - Tests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Other