Epic Goal

• Further expand Deppy plug-in-ability by moving sourcing of content from (directly talking to) catalog sources to an external component that interfaces Deppy and CatalogSources (e.g. a DeppySource)

Why is this important?

• Makes Deppy agnostic to entity/constraint sourcing - anything that implements the requisite interface can be a source for Deppy

Scenarios

1. New CatalogSources can be easily integrated into Deppy
2. Clients can choose the data sources they use for resolution

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 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>