Skip to content
SHC Docs

shc config

view and set configuration

Reference for the config CLI group. Source: modules/config/commands/.

SubcommandDescription
editedit config in an editor
getget a config value
listlist all config values
setset a config value
unsetunset a config value

edit config in an editor

FlagTypeRequiredHelp
--scopestrnoscope to edit: global, tenant, environment, stack, deployment

Source: modules/config/commands/

get a config value

FlagTypeRequiredHelp
--scopestrnoscope: global, tenant, environment, stack, deployment
--dbboolnouse database-backed config

Source: modules/config/commands/

list all config values

FlagTypeRequiredHelp
--scopestrnofilter by scope: global, tenant, environment, stack, deployment
--prefixstrnofilter by path prefix

★ A bare shc config ls lists GLOBAL rows only. The listing walks the scope tiers whose identifiers you supplied, and always includes global, so with no -t/-s/-e there is nothing else to walk. Rows set at tenant, environment, stack or deployment scope are not in the output, and their absence looks identical to a key nobody ever set.

Measured on a live estate: shc config ls returned 26 rows and no launcher; shc config ls -t corp returned 28 and revealed launcher = auto at tenant scope. When you are auditing “is this key set anywhere?”, pass the tenant, or ask per tier with --scope:

Terminal window
shc config ls # global only
shc config ls -t corp # + that tenant's rows
shc config ls -t corp -s web -e prod # + stack and deployment rows
shc config get <key> # the resolved value, all layers

shc config get is the right tool for “what is in effect”: it walks the full cascade (deployment > stack > environment > tenant > global, under files and defaults) rather than one tier of DB rows.

Source: modules/config/commands/

set a config value

FlagTypeRequiredHelp
--scopestrnoscope: global, tenant, environment, stack, deployment
--dbboolnouse database-backed config

Source: modules/config/commands/

unset a config value

FlagTypeRequiredHelp
--scopestrnoscope: global, tenant, environment, stack, deployment
--dbboolnouse database-backed config

Source: modules/config/commands/