Skip to content

Latest commit

 

History

History
116 lines (80 loc) · 3.78 KB

ocm_bootstrap_configuration.md

File metadata and controls

116 lines (80 loc) · 3.78 KB

ocm bootstrap configuration — Bootstrap TOI Configuration Files

Synopsis

ocm bootstrap configuration [<options>] {<component-reference>} {<resource id field>}

Aliases

configuration, config, cfg

Options

  -c, --credentials string   credentials file name (default "TOICredentials")
  -h, --help                 help for configuration
      --lookup stringArray   repository name or spec for closure lookup fallback
  -p, --parameters string    parameter file name (default "TOIParameters")
      --repo string          repository name or spec

Description

If a TOI package provides information for configuration file templates/prototypes this command extracts this data and provides appropriate files in the filesystem.

The package resource must have the type toiPackage. This is a simple YAML file resource describing the bootstrapping of a dedicated kind of software. See also the topic ocm toi-bootstrapping.

The first matching resource of this type is selected. Optionally a set of identity attribute can be specified used to refine the match. This can be the resource name and/or other key/value pairs (<attr>=<value>).

If no credentials file name is provided (option -c) the file TOICredentials is used. If no parameter file name is provided (option -p) the file TOIParameters is used.

For more details about those files see ocm bootstrap package.

If the --repo option is specified, the given names are interpreted relative to the specified repository using the syntax

<component>[:<version>]

If no --repo option is specified the given names are interpreted as located OCM component version references:

[<repo type>::]<host>[:<port>][/<base path>]//<component>[:<version>]

Additionally there is a variant to denote common transport archives and general repository specifications

[<repo type>::]<filepath>|<spec json>[//<component>[:<version>]]

The --repo option takes an OCM repository specification:

[<repo type>::]<configured name>|<file path>|<spec json>

For the Common Transport Format the types directory, tar or tgz is possible.

Using the JSON variant any repository types supported by the linked library can be used:

Dedicated OCM repository types:

  • ComponentArchive: v1

OCI Repository types (using standard component repository to OCI mapping):

  • CommonTransportFormat: v1
  • OCIRegistry: v1
  • oci: v1
  • ociRegistry


If a component lookup for building a reference closure is required the --lookup option can be used to specify a fallback lookup repository. By default, the component versions are searched in the repository holding the component version for which the closure is determined. For Component Archives this is never possible, because it only contains a single component version. Therefore, in this scenario this option must always be specified to be able to follow component references.

Examples

$ ocm toi bootstrap config ghcr.io/mandelsoft/ocm//ocmdemoinstaller:0.0.1-dev

SEE ALSO

Parents

  • ocm bootstrap — bootstrap components
  • ocm — Open Component Model command line client
Additional Links