get artifacts
On this page
Usage
ocm get artifacts [<options>] {<artifact-reference>}Options
-a, --attached show attached artifacts
-h, --help help for artifacts
-o, --output string output mode (JSON, json, tree, wide, yaml)
-r, --recursive follow index nesting
--repo string repository name or spec
-s, --sort stringArray sort fieldsDescription
Get lists all artifact versions specified, if only a repository is specified all tagged artifacts are listed.
If the repository/registry option is specified, the given names are interpreted relative to the specified registry using the syntax
<OCI repository name>[:<tag>][@<digest>]
If no –repo option is specified the given names are interpreted
as extended OCI artifact references.
[<repo type>::]<host>[:<port>]/<OCI repository name>[:<tag>][@<digest>]
The –repo option takes a repository/OCI registry specification:
[<repo type>::]<configured name>|<file path>|<spec json>
For the Common Transport Format the types directory,
tar or tgz are possible.
Using the JSON variant any repository types supported by the linked library can be used:
ArtifactSet: v1CommonTransportFormat: v1DockerDaemon: v1Empty: v1OCIRegistry: v1oci: v1ociRegistry
With the option –recursive the complete reference tree of a index is traversed.
With the option –output the output mode can be selected.
The following modes are supported:
(default)JSONjsontreewideyaml
Examples
$ ocm get artifact ghcr.io/open-component-model/ocm/component-descriptors/ocm.software/ocmcli
$ ocm get artifact ghcr.io/open-component-model/ocm/ocm.software/ocmcli/ocmcli-image:0.17.0See Also
- ocm get — Get information about artifacts and components