opschain admin transport-providers test
packs:rpc
Validates a transport provider record without dialling any host: the
stored config re-parses against the kind's schema and the referenced
credential resolves and parses as what the config says it is (for
ssh-static with auth_method: key, an SSH private key; with
password, a resolvable value; for ssh-ca, the CA signing key must
parse and sign a probe certificate, which is discarded in memory — a
passphrase-protected CA key fails, since the platform cannot sign with
it). A provider-qualified reference checks
its named secrets provider is enabled. The typed outcome rides the
response and is recorded as the record's health (last_test_at /
last_test_success / last_test_error, surfaced by the list and show
verbs). A failing validation is a successful command: the failure reason
prints — naming the reference, never a value — and the exit code
stays 0.
opschain admin transport-providers test prod-ssh
Transport provider prod-ssh: record validation succeeded
opschain admin transport-providers test prod-ssh
Transport provider prod-ssh: record validation FAILED — the referenced credential does not resolve: no vault value at "secret-vault://transport-providers/prod-ssh/credential"
-o, --output json|yaml emits {"provider": "...", "success": true|false}
plus failure_reason on failure. The 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-transport-providers-show— the recorded health.