opschain admin secrets providers test
Included from Basic tier
Probes a secrets provider the way resolution would use it: authenticate
with the stored credential per the auth method (a userpass/approle
probe performs the login; token auth proves the token directly via a
self-lookup), over the connection's TLS posture. The typed outcome rides
the response and is recorded as the connection's health
(last_test_at / last_test_success / last_test_error, surfaced by the
list and show verbs) — the honest replacement for finding out at step
time. A failing probe is a successful command: the failure reason prints
and the exit code stays 0.
opschain admin secrets providers test vault
Secrets provider vault: connection test succeeded
opschain admin secrets providers test vault
Secrets provider vault: connection test FAILED — vault token self-lookup: ... connection refused
-o, --output json|yaml emits {"provider": "...", "success": true|false}
plus failure_reason on failure. The probe outcome is audited (success
flag only — never credential material).
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-providers-show— the recorded health.