Description
When called on a CTF without specifying a component name, the OCM CLI v2 command ocm get cv should list all components and their versions contained there.
This form requires significant extensions to the existing OCM Repository structure:
- We require a
ComponentVersionRepositoryLister Interface that is implemented to be able to list ComponentVersionRepositories:
- The list should be unique by name
- The list should be able to point back to the original repository where you can retrieve versions
- This needs to be implemented primarily by CTFs
- Afterwards we need an extension of the Plugin Contract for Component Versions (@Skarlso for reference)
- Once this is done, ocm get cv needs to work for ctf repositories if there is no component specified (likely adjustment to component reference parsing, but needs investigation)
- After this, if there is a CTF specification, and we have no component name, attempt to lookup component names via the new Interface. If successful, extend the call to list all versions for all components.
This should later on be extendable for docker registries so we can use the catalog API for example.
Done Criteria
Description
When called on a CTF without specifying a component name, the OCM CLI v2 command
ocm get cvshould list all components and their versions contained there.This form requires significant extensions to the existing OCM Repository structure:
ComponentVersionRepositoryListerInterface that is implemented to be able to list ComponentVersionRepositories:This should later on be extendable for docker registries so we can use the catalog API for example.
Done Criteria