ocm add componentversions — Add Component Version(S) To A (New) Transport Archive

Synopsis:
  ocm add componentversions [<options>] [--version <version>] [<ctf archive>] {<component-constructor.yaml>}

Aliases:
  componentversions, componentversion, cv, components, component, comps, comp, c

Options:
      --addenv                    access environment for templating
  -C, --complete                  include all referenced component version
  -L, --copy-local-resources      transfer referenced local resources by-value
  -V, --copy-resources            transfer referenced resources by-value
  -c, --create                    (re)create archive
      --dry-run                   evaluate and print component specifications
  -F, --file string               target file/directory (default "transport-archive")
  -f, --force                     remove existing content
  -h, --help                      help for componentversions
      --lookup stringArray        repository name or spec for closure lookup fallback
  -O, --output string             output file for dry-run
  -P, --preserve-signature        preserve existing signatures
  -R, --replace                   replace existing elements
  -S, --scheme string             schema version (default "v2")
  -s, --settings stringArray      settings file with variable settings (yaml)
      --skip-digest-generation    skip digest creation
      --templater string          templater to use (go, none, spiff, subst) (default "subst")
  -t, --type string               archive format (directory, tar, tgz) (default "directory")
      --uploader <name>=<value>   repository uploader (<name>[:<artifact type>[:<media type>[:<priority>]]]=<JSON target config>) (default [])
  -v, --version string            default version for components

Description:

  Add component versions specified by a constructor file to a Common Transport
  Archive. The archive might be either a directory prepared to host component version
  content or a tar/tgz file (see option --type).

  If option «--create» is given, the archive is created first. An
  additional option «--force» will recreate an empty archive if it
  already exists.

  If option «--complete» is given all component versions referenced by
  the added one, will be added, also. Therefore, the «--lookup» is required
  to specify an OCM repository to lookup the missing component versions. If 
  additionally the «-V» is given, the resources of those additional
  components will be added by value.

  The «--replace» option allows users to specify whether adding an
  element with the same name and extra identity but different version as an 
  existing element, append (false) or replace (true) the existing element.

  The «--preserve-signature» option prohibits changes of signature 
  relevant elements.

  The source, resource and reference list can be composed according to the commands
  «ocm add sources», «ocm add resources», «ocm add references»,
  respectively.

  The description file might contain:
  - a single component as shown in the example
  - a list of components under the key «components»
  - a list of yaml documents with a single component or component list
  The optional field «meta.configuredSchemaVersion» for a component
  entry can be used to specify a dedicated serialization format to use for the
  component descriptor. If given it overrides the «--schema» option
  of the command. By default, v2 is used.

  Various elements support to add arbitrary information by using labels
  (see «ocm ocm-labels»).

  The «--type» option accepts a file format for the
  target archive to use. It is only evaluated if the target 
  archive does not exist yet. The following formats are supported:
  - directory
  - tar
  - tgz
  The default format is «directory».