Description of problem:
Currently, when using `opm index export` to backfill the index image back to the appregistry nested directory format, opm generates the set of bundles included in a package and pulls the csvs for each bundle into the directory. Since those bundles become the source of truth for all graph information, any mode that takes that source of truth away from the replaces chain in the set of csvs is lost. Instead, opm should respect the changes made to the graph defined in the index image and modify the exported manifests to generate a replaces graph that properly encapsulates the information generated by index add commands using semver and semver-skippatch modes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a set of bundles that do not have `replaces` set in their csvs using `opm index add` to an index image
2. `opm index export` that index image
The csvs do not have replaces set, the graphs those bundles represent will not link all of the bundles down from latest version to oldest version.
Exported csvs have replaces set properly so that the eventual app-registry blob can be unpacked by a cluster at runtime with the correct graph as defined in the index image.
*** Bug 1889716 has been marked as a duplicate of this bug. ***
Any estimation of when this will be ready?
This is assigned to be worked on in the upcoming sprint.
Moving this to low, this bug potentially affects the pipelines team but they have no immediate plans to switch to semver mode for index building. See https://docs.google.com/document/d/1GWUPp2CivPWvL0IWOndZu9WX48oNmd4Cp9nCkM0QkeM