Epic Goal

Make sure all SDK commands being used by the pipeline teams (e.g. in CVP or in ISV Preflight Checks) that build catalogs works well with the file-based catalog (FBC).

Why is this important?

OLM and PE team is actively working on a more flexible and human-readable way to manage Operator catalogs (aka, file-based catalog, FBC) for Operator authors to strategize in how to publish their Operator releases.

For Operator SDK, we want to make sure all SDK commands being used by the pipeline teams, e.g. in CVP or in ISV Preflight Checks work well with the file-based Catalog.

Scenarios

• Operator bundle can be running on an FBC-enabled cluster using `run bundle` command with OLM.

• A new version Operator bundle can be upgraded on an FBC-enabled cluster right after `run bundle` command using `run bundle upgrade` command with OLM.

• A new version Operator bundle can be upgraded from an existing bundle version in an existing on-cluster FBC using `run bundle upgrade` command with OLM.

• A new version Operator bundle can be upgraded from an existing bundle version in an existing on-cluster sqlite-based catalog using `run bundle upgrade` command to build an FBC with OLM.

Acceptance Criteria

• "run bundle” command can build a new file-based catalog with a new bundle added for testing running with OLM.

• “run bundle upgrade" commands can extract a bundle from both sqlite and file-based catalog and build a new file-based catalog with the new bundle version added for testing upgrading with OLM.

Engineering Notes 

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>