filter by scope: global, tenant, environment, stack, deployment
--prefix
str
no
filter 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
shcconfigls# global only
shcconfigls-tcorp# + that tenant's rows
shcconfigls-tcorp-sweb-eprod# + stack and deployment rows
shcconfigget<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.