shc config set
shc config set
Section titled “shc config set”set a config value (key! removes it)
Synopsis
Section titled “Synopsis”Set a config value, or remove one with a trailing ’!’.
shc config set log.level debug # set shc config set log.level! # remove, at this scope only
With no --scope the row lands at the narrowest tier -t, -s and -e name, and is global when none is given. A tenant or environment left out is the one shc install would use.
A removal deletes the row at exactly the scope a set with the same flags would have written, and nothing else. The cascade may then reveal a value from a broader scope, which is the intended effect of dropping an override.
shc config set <key> <value> [flags]Options
Section titled “Options” -h, --help help for set --location string the location path a location-scoped row is for (covers every node at or below it) --node string the node a node-scoped row is for, by name --scope string scope (global|tenant|environment|stack|deployment|node|location)Options 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) -e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default") --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) -s, --stack string stack name (default: $SHC_STACK) -t, --tenant string tenant name (default: $SHC_TENANT) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc config - view and set configuration
shc@docs:~$