Command 'juju update-secret-backend'

See also: How to manage secret backends

Usage:

juju update-secret-backend [options] <backend-name>

Summary:

Update an existing secret backend on the controller.

Global Options:

--debug  (= false)

Equivalent to --show-log --logging-config=<root>=DEBUG

-h, --help  (= false)

Show help on a command or other topic.

--logging-config (= "")

Specify log levels for modules

--quiet  (= false)

Show no informational output

--show-log  (= false)

If set, write the log file to stderr

--verbose  (= false)

Show more verbose output

Command Options:

-c, --controller (= "")

Controller to operate in

--config  (= )

Path to yaml-formatted configuration file

--force  (= false)

Force update even if the backend is unreachable

--reset  (= )

Reset the provided comma delimited config keys

Details:

Updates a new secret backend for storing secret content.

You must specify a name for the backend to update, followed by any necessary backend specific config values. Config may be specified as key values ot read from a file. Any key values override file content if both are specified.

Config attributes may be reset back to the default value using --reset.

To rotate the backend access credential/token (if specified), use the “token-rotate” config and supply a duration. To reset any existing token rotation period, supply a value of 0.

Examples:

juju update-secret-backend myvault --config /path/to/cfg.yaml
juju update-secret-backend myvault name=myvault2
juju update-secret-backend myvault token-rotate=10m --config /path/to/cfg.yaml
juju update-secret-backend myvault endpoint=https://vault.io:8200 token=s.1wshwhw
juju update-secret-backend myvault token-rotate=0
juju update-secret-backend myvault --reset namespace,ca-cert

See also:

add-secret-backends
list-secret-backends
remove-secret-backend
show-secret-backend

Last updated 9 months ago.