[DUPLICATE]As a oc-mirror user, I would like mirrored operator catalogs to have valid caches

As a oc-mirror user, I would like mirrored operator catalogs to have valid caches that reflect the contents of the catalog (configs folder) based on the filtering done in the ImageSetConfig for that catalog

so that the catalog image starts efficiently in a cluster.

Tasks:

• white-out /tmp on all manifests (per platform)
• Recreate the cache under /tmp/cache using
  • extract the whole catalog
  • use the opm binary included in the extracted catalog to call (command line)

opm serve /configs –-cache-dir /tmp/cache –-cache-only 

• Create a new layer from /configs and /tmp/cache
  • the /tmp is compatible with all platforms
• oc-mirror should not change the CMD nor ENTRYPOINT of the image
• Rebuild catalog image up to the index (manifest list)

Acceptance criteria:

• Run the catalog container with command opm serve <configDir> --cache-dir=<cacheDir> --cache-only --cache-enforce-integrity to verify the integrity of the cache
• 4.14 catalogs mirrored with oc-mirror v4.14 run correctly in a cluster
  • when mirrored with mirrorToMirror workflow
  • when mirrored with mirrorToMirror workflow with --include-oci-local-catalogs
  • when mirrored with mirrorToDisk + diskToMirror workflow
• 4.14 catalogs mirrored with oc-mirror v4.14 use the pre-computed cache (not sure how to test this)
• catalogs<= 4.13 mirrored with oc-mirror v4.14 run correctly in a cluster (this is not something we publish as supported)