Description
The goal of this EPIC is to extend the set of supported Repository Operations by operations for maintaining aliases (floating tags) for ocm component versions.
This feature was requested by early adopters of the ocm tooling.
We decided to support tags for oci based ocm repositories. This was also added to the OCI Storage Backend Specification. To keep the concept open to further implementations (besides OCI), we referred to the concept more generically as version aliasing.
The trade off of promoting this as a first class ocm repository operation is that this further constraints the storage backends on which ocm repositories could potentially be implemented to storage backends that can somehow support the alias concept.
Currently, the only other repository storage backend that might be planned besides OCI and CTF (which is essentially OCI), is S3.
User Story
As an ocm user, I want to be able to refer to ocm component versions through floating tags such as latest or stable. Also, I want to be able to resolve component versions such as latest efficiently without having to list all the versions and perform a client side semver filtering.
Scope
List all deliverables that are part of this epic. The Epic is considered DONE if all of the below mentioned deliverables are available.
Description
The goal of this EPIC is to extend the set of supported Repository Operations by operations for maintaining aliases (floating tags) for ocm component versions.
This feature was requested by early adopters of the ocm tooling.
We decided to support tags for oci based ocm repositories. This was also added to the OCI Storage Backend Specification. To keep the concept open to further implementations (besides OCI), we referred to the concept more generically as version aliasing.
The trade off of promoting this as a first class ocm repository operation is that this further constraints the storage backends on which ocm repositories could potentially be implemented to storage backends that can somehow support the
aliasconcept.Currently, the only other repository storage backend that might be planned besides OCI and CTF (which is essentially OCI), is S3.
User Story
As an ocm user, I want to be able to refer to ocm component versions through floating tags such as
latestorstable. Also, I want to be able to resolve component versions such aslatestefficiently without having to list all the versions and perform a client side semver filtering.Scope
List all deliverables that are part of this epic. The Epic is considered DONE if all of the below mentioned deliverables are available.
- create issues to push the implementation, specification extension and documentation
- update the ADR with the rationale for rejecting the proposal and reduce the EPIC scope for OCI implementation