1. Proposed title of this feature request

oc-mirror support using the same tarball for multiple catalog image names/tags

2. What is the nature and description of the request?

Nowadays the tarball is created using the targetCatalog/targetTag information in the ImageSetConfiguration so even if it contains the exact same information it can't be used to push the content to a new catalog image with a different name/tag.

3. Why does the customer need this? (List the business requirements here)

Customers in disconnected environments need to create a tarball from a connected environment, copy it to the right place and then run the diskToMirror.
If a customer wants to use the same tarball to populate different internal registries where the targetCatalog/targetTag value is different from the original one, the tarball is uselesss as oc-mirror v2 doesn't work and the customer needs to run the mirrorToDisk again to create a new tarball.

Being able to override the targetCatalog/targetTag values when doing diskToMirror would help with these long process where big tarballs need to be created and copied over the network. This loop can lead to extra costs in traffic and disk space being used and charged in cloud environments, where a single tarball would be enough (as the content of the mirror is the same and the only change is the destination catalog image name and tag).

4. List any affected packages or components.

oc-mirror plugin v2