opschain admin secrets bindings list

Included from Basic tier

Lists every declared scope binding, scope path ascending: the bound provider's code, its enabled state, its last-test health (- until the test verb first runs, then ok/failing) and the binding row id — the posture view answering which parts of the estate resolve against an unhealthy provider.

opschain admin secrets bindings list
SCOPE                               PROVIDER  ENABLED  HEALTH   ID
/                                   vault     yes      ok       019a0d7e-10c2-7f7a-8b53-3b1c9a4f2e10
/projects/payments                  payments  yes      failing  019a0d7e-10c2-7f7a-8b53-3b1c9a4f2e11

-o, --output json|yaml emits the binding rows as a machine document.

Flags

Flag	Meaning
--server <url>	Server base URL (default: the active context / OPSCHAIN_SERVER).
--auth-token <token>	Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login).
--filter <column>[!]=<value>	Keep only rows matching the term (repeatable; terms AND). Columns are the printed table headers lowercased; * wildcards match the whole cell case-insensitively, != negates, commas mean any-of. Applied client-side. Grammar: opschain docs cli.

See also

• opschain docs cli/admin-secrets-bindings-resolve — provenance for one node path.