shc vault
shc vault set
Section titled “shc vault set”Set a secret. Both the key and the value are positional and both are
required. There is no --generate; secrets that SHC mints for you are
requested from an app’s vars.yaml with ref+vault://<key>?autogen:
shc vault set db_password mypassword123shc vault set api_key secret123 --scope globalshc vault set admin_password s3cure! --scope tenantshc vault get
Section titled “shc vault get”Retrieve a secret:
shc vault get db_passwordshc vault get db_password --stack myappshc vault get db_password --stack myapp --environment prodget takes no --scope: you do not name a tier, you name a context
with -s/--stack and -e/--environment, and resolution cascades from
most precise (deployment) to least precise (global). --scope is a write
and filter flag: it exists on set, rm and ls.
shc vault exists
Section titled “shc vault exists”Check if a secret exists. Like get, it takes a context rather than a
--scope:
shc vault exists db_passwordshc vault exists db_password --stack myappshc vault ls
Section titled “shc vault ls”List secrets:
shc vault lsshc vault ls --scope tenantshc vault ls --output jsonshc vault rm
Section titled “shc vault rm”Remove a secret:
shc vault rm old_password -yshc vault rm temp_key --scope deployment -yshc vault rm old_password --scope global -ySee Also
Section titled “See Also”shc@docs:~$