tags

Usage

ocm show tags [<options>] <component> {<version pattern>}

Options

  -h, --help          help for tags
  -l, --latest        show only latest tags
      --repo string   repository name or spec
  -o, --semantic      show semantic tags
  -s, --semver        show only semver compliant tags

Description

Match tags of an artifact against some patterns.

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: v1
  • CommonTransportFormat: v1
  • DockerDaemon: v1
  • Empty: v1
  • OCIRegistry: v1
  • oci: v1
  • ociRegistry

Examples


$ oci show tags ghcr.io/mandelsoft/kubelink

See Also