rsigma config show

rsigma config show

Print the effective configuration after all layers have been merged, annotated with the layer each value came from.

Synopsis

rsigma config show [--config <PATH>] [--for <global|daemon|eval>] [--format <text|json|yaml>]

Description

Resolves the config the same way engine daemon and engine eval do at startup, except that this command stops short of the CLI-flag layer (it has no live command-line to read flags from). Concretely it folds:

1. compiled defaults
2. discovered config files (system → user → .rsigmarc → ./rsigma.yaml, or --config)
3. the RSIGMA_* environment layer

into a single tree, and reports the winning layer for every leaf. To inspect what a specific live invocation would resolve to, including the flag layer, use --dry-run on engine daemon or engine eval instead.

Flags

Output

Text mode

One line per leaf: <dotted.path> = <value> (<source>). The source is one of default, file, env, or flag (flag only appears in command --dry-run output, never here).

daemon.api.addr = 127.0.0.1:7777  (env)
daemon.input.batch_size = 128  (default)
daemon.input.buffer_size = 50000  (file)

JSON mode

An envelope that pairs the resolved tree with the per-leaf source map.

{
  "config": {
    "daemon": { "api": { "addr": "9.9.9.9:1" } }
  },
  "sources": {
    "daemon.api.addr": "file"
  }
}

YAML mode

Just the resolved tree, suitable for piping back into the file layer.

Exit codes

Examples

See what a daemon would use, with the env layer applied:

RSIGMA_DAEMON__API__ADDR="127.0.0.1:7777" rsigma config show --for daemon

Round-trip the effective config to a new file:

rsigma config show --format yaml > effective.yaml

Diff what your repo’s .rsigmarc adds on top of the user defaults:

diff <(rsigma config show --config ~/.config/rsigma/config.yaml --format yaml) \
     <(rsigma config show --format yaml)

See also

• config validate to surface unknown keys and inactive sections.
• Configuration Reference for the precedence model.