Zum Hauptinhalt springen
Version: Weekly Build

oms template config

Generated from OMS version v2.113.0.

Render a config.yaml template using secrets from a vault file

Synopsis​

Render a config.yaml template using secrets from a prod.vault.yaml file.

This command prints the rendered configuration to stdout so templating can be tested without running an installation.

Template syntax in config.yaml:

Inject a secret value (defaults to the "content"/"password" field)

someKey: '{{ secret "mySecret" }}'

Select a specific field

username: '{{ secret "mySecret" "fields.username" }}' password: '{{ secret "mySecret" "fields.password" }}'

Inject a file secret's content

caCert: '{{ secret "caCert" "file.content" }}'

Secret names and selectors must match entries in the prod.vault.yaml file.

oms template config [flags]

Examples​

# Render config.yaml with secrets from prod.vault.yaml
$ oms template config --config config.yaml --vault prod.vault.yaml --age-key age_key.txt

Options​

  -k, --age-key string      Path to the age key file (required for sops unless an age key environment variable is set)
  -c, --config string       Path to the config.yaml template to render (required)
  -h, --help                help for config
  -v, --vault string        Path to the prod.vault.yaml file (required)
      --vault-type string   Vault storage type (sops or plain) (default "sops")

Options inherited from parent commands​

      --verbose   Enable verbose output

SEE ALSO​