Skip to content
SHC Docs

shc vault get

get a secret value

Read a secret. Without --scope the read walks the cascade (deployment, stack, environment, tenant, global) and answers with the first tier that has a row, which is what every consumer of the secret does too.

With --scope the read targets one tier and reports X404907SECNOF when that tier is empty, even if a broader one holds a value. That is how you find out which row a value came from: set could name a scope and get could not, and a write that had landed on a tier nothing read was invisible from the CLI for exactly that reason.

shc vault get <key> [flags]
shc vault get -t master -s keycloak -e default admin_password
shc vault get -t master -s keycloak -e default --scope tenant admin_password
-e, --environment string environment name
-h, --help help for get
--scope string read this exact scope tier (global|tenant|stack|environment|deployment) instead of walking the cascade
-s, --stack string stack name
--config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win
-d, --debug enable debug mode (default: $SHC_DEBUG)
--exclude string comma-separated dotted paths to drop
--fields string comma-separated columns/keys to show (and their order)
--filter string comma-separated dotted paths to keep (drops everything else)
-o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT)
-p, --password string vault password (visible in the process list, prefer --password-file)
--password-file string read the vault password from a file (mode 0600 expected); use '-' to read stdin. Takes precedence over --password and never puts the secret in argv
-t, --tenant string tenant name (default: $SHC_TENANT)
-v, --verbose verbose output (default: $SHC_VERBOSE)