opschain admin secrets bindings resolve
Included from Basic tier
Answers resolution provenance for a node path: which provider governs it
and which scope binding decided — the deepest covering scope, or the
single-enabled default when nothing binds ("no binding declared"). With
several providers enabled and no covering binding (not even /), the verb
refuses by name rather than guessing, matching resolution itself.
opschain admin secrets bindings resolve /projects/payments/environments/prod
Provider: payments (https://payments-bao.corp:8200)
Decided by: binding /projects/payments
Health: ok
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). |
See also
opschain docs cli/admin-secrets-bindings-list— every binding with provider health.