Epic Goal

• Integrate the Operator API with Deppy Library
• Ensure integration works well in the initial OLM v1 Milestone 1 goal of enabling basic install/uninstall of operators

Why is this important?

• The Operator API will delegate to Deppy for package selection.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• The Operator Controller is able to transform existing Operator CRs into PackageNameconstraints
• The Operator Controller specifies GVK Uniqueness Constraints
• The Operator Controller can feed Constraints and Deppy Sources into the Deppy Solver
• The Deppy Solver returns a solution or an error explaining why the set of constraints cannot be satisfied.

Dependencies (internal and external)

1. N/A

Previous Work (Optional):

1. N/A

Upstream Link:

• https://github.com/operator-framework/operator-controller/issues/63

Open questions:

1. N/A

Done Checklist

• CI - CI is running, tests are automated and merged.
• 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>