Skip to content

cwp config get

shipped 1.0.0
cwp config get [key] [flags]

Local only — it acts on no environment.

ArgumentWhat it isDefault
[key]dotted path, e.g. pull.uploads
FlagWhat it doesDefault
--explainshow every layer of the chain, and which one winsoff

Plus the shared flags --json, --verbose and --dry-run.

What it does

Prints one key, or every key, with the value and where it came from.

A key you never wrote still has a value, because the schema has a default — and those are not the same thing, so the output distinguishes them:

✓ pull.uploads — proxy
✓ pull.scrub — true (default)
– builder.options.wp_user — not set — who ability calls run as

A single key’s value goes to stdout, so it substitutes:

cd "$(cwp config get builder.options.export_dir)"

The listing and everything else stay on stderr.

--explain says which layer a run will actually obey

What your file says is not always what happens: pull.uploads and defaults.uploads are two layers of one question, and a flag beats both. --explain prints the chain and marks the winner:

✓ pull.uploads — proxy
pull.uploads resolves to proxy from the project layer:
    flag     —
  → project  proxy
    machine  —
    default  proxy

A key with no second layer says so rather than drawing a table for one row — docroot is written in one place and read from there.

What it does not do

It writes nothing and contacts nothing. --dry-run is accepted and ignored.