Implement OCM OCI Repository Mapping for deleting Component Versions

[sk31337]

Description

I have created too many componentversions on my oci registry:

ocm get componentversions secret.oci.registry.very.secret/ocm//foo/bar
COMPONENT                 VERSION           PROVIDER
foo/bar 0.0.2-61-g6ba43a8 fubar
foo/bar 0.0.2-68-gc6b97e1 fubar
foo/bar 0.1.1-1-ga5a48ab  fubar
foo/bar 0.1.1-25-g03d7a5a fubar
foo/bar 0.1.1-4-gf608d3c  fubar
foo/bar 0.1.2-18-gb3d73c1 fubar
foo/bar 0.1.2-3-gd008b85  fubar
foo/bar 0.1.2-6-gdfa6567  fubar
foo/bar 0.1.2-9-ge86e0ee  fubar
foo/bar 0.1.3             fubar
foo/bar 0.1.4             fubar

I wish there is another way to delete e.g. componentversion 0.0.2-61-g6ba43a8 and its resources other than deleting the oci artifacts via web-ui.

Therefore i request a new sub-command ocm delete to delete OCM artifacts from a specific OCI registry.

Suggestions for sub-command syntax & functionality:

• delete a specific componentversion from an oci registry ocm delete componentversion secret.oci.registry.very.secret/ocm//foo/bar:0.0.2-61-g6ba43a8
• delete a specific componentversion with its component references from an oci registry ocm delete componentversion secret.oci.registry.very.secret/ocm//foo/bar:0.0.2-61-g6ba43a8 -r
• delete a specific componentversion with its resources from an oci registry ocm delete componentversion secret.oci.registry.very.secret/ocm//foo/bar:0.0.2-61-g6ba43a8 -A (-A for ALL)
• delete a all componentversions an oci registry ocm delete componentversions secret.oci.registry.very.secret/ocm//foo/bar (-r & -A also applies for)

Potential challenges:

• check during deletion of componentversion 0.0.2-61-g6ba43a8 if the resources linked in componentversion 0.0.2-61-g6ba43a8 are used in other componentversions

Feel free to reach out.