shc vault import
shc vault import
Section titled “shc vault import”import an encrypted bundle into the vault
Synopsis
Section titled “Synopsis”Import a password-encrypted bundle produced by shc vault export.
When —password is omitted the command prompts for one. Secrets keep
their original scope unless retargeted with —tenant / —stack /
—environment / —deployment or —remap-scope (tenant=X,stack=Y,…);
existing secrets at the target scope are skipped unless —overwrite.
Use ”-” as the input file to read the bundle from stdin. Prints the
imported/updated/skipped counts.
shc vault import <input-file> [flags]Examples
Section titled “Examples” shc vault import secrets.enc shc vault import secrets.enc --overwrite shc vault import myblog.enc --remap-scope tenant=acme,stack=myblog shc vault import - -P s3cret < secrets.encOptions
Section titled “Options” --deployment string target deployment override -e, --environment string target environment override -h, --help help for import --overwrite overwrite existing secrets at the target scope -P, --password string import password (prompts when empty) --remap-scope string remap source scope: tenant=X,stack=Y,environment=Z,deployment=W -s, --stack string target stack override --tenant string target tenant overrideOptions inherited from parent commands
Section titled “Options inherited from parent commands” --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) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc vault - manage secrets and credentials
shc@docs:~$