Summary / Background

• Deppy Source

Acceptance Criteria

• DeppySource that can interface with CatalogSources implemented
• DeppySource can retrieve/query information and build entities (GetEntities API)
• Identify how to model entities, which have an ID and Properties 
  • Identify how to structure Properties to fully capture all metadata needed for resolution and for referencing bundle/packages uniquely in an ActiveResolution
    • Properties will be a key/value map that specify dependencies and other metadata (maxOCP version) that constraints can be extracted from by the Constraint Builder
  • ID must be globally unique and represents a specific bundle/package
    • package name + version + catalog source name (or deppy source ID) + channel

Assumptions

• Assume, for now, that an entity maps to a bundle

Definition of Done

• Unit tests

Upstream Github issue: https://github.com/operator-framework/deppy/issues/49