Epic Goal

• Integrate the dependency solver into Deppy replacing the direct queries to CatalogSources
• Source cluster runtime constraints (i.e. MaxOCPVersion and MinKubeVersion) from an external component using a common interface understood by Deppy

Why is this important?

• With a solver at its core, Deppy can be used for proper dependency management including resolving packages with dependencies.
• By sourcing the cluster runtime constraints via an external component, Deppy takes a step in the direction of being able to collect constraints at runtime from other cluster components using behind a common interface - making it extensible.

Scenarios

1. Platform operators defines a list of packages it wishes to install including allowed version ranges. The solver should succeed with the list of packages that should be available on cluster, or fail with a meaningful error.
2. Version ranges defined for the package are respected by the solver.
3. Any package/bundle properties required to locate Platform Operators should be respected by the solver.
4. When a new package version is made available, the solution is updated to include the new package, as long as the update graph is respected.
5. Dependency resolution should be demonstrable - though not required for Platform Operators.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. Previous Deppy Milestone (link to come)

Previous Work (Optional):

1. …

Open questions::

1. …

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>