User Story

As a user I would provide entities, over which I will apply constraints, over the network

Summary / Background

DeppySource Adapters will be sub-framework of the Deppy framework that will facilitate the transformation of online resource into entities and the querying of those entities

Acceptance Criteria

• A generic API (rest, or grpc, etc.) to get all entities (we'll start with client side caching/querying)
• It is easy for users to provide a transform function from whatever domain they are into a pool of entities
• This will probably end up in its own repository eventually, therefore it should be placed in its own package s.t. it can just be yanked from the code-base without side-effects (aside from recalculating project dependencies for go.mod)

Scenarios

• I have an [OLM CatalogSource](https://olm.operatorframework.io/docs/concepts/crds/catalogsource/) and would like to provide the contained bundles as entities for resolution

Assumptions

• We assume that this will be a first pass at the api and doesn't need to be performance optimized yet.
• We'll start with client-side caching/querying and there will not be any caching in the server for now.

Links (docs, drawings, designs, etc)

[Deppy-as-a-Framework](https://hackmd.io/fDfcLKNzRPCgILMIQ8aPOw?view#Appendix-III-Deppy-as-a-Framework)

Dependencies

Definition of Done

• unit tests
• extensive godoc (this is a framework after all)
• documentation of framework/design as necessary
• reviewed and merged

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