Skip to main content
Version: v5.6.1

opschain admin transport-providers update

packs:rpc

Updates a transport provider by code or id. Only the flags you pass change; the code and kind are immutable. A supplied --credential-ref re-pins the reference (resolved as it is set, exactly like create); an inline credential via --credential-env / --credential-prompt rotates the vault value under transport-providers/<code>/credential and re-pins — rotation happens in one place, and nothing is ever echoed back.

Re-enabling a disabled provider requires the packs:rpc entitlement; disabling never does (lapse cleanup stays open).

ROTATED_KEY=$(cat ~/.ssh/new_deploy_key) opschain admin transport-providers update prod-ssh \
--credential-env ROTATED_KEY
Updated transport provider prod-ssh

Flags​

FlagMeaning
--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).
--display-name <name>Human-readable provider name.
--config <json>Replacement kind-specific config as a JSON object.
--credential-ref <ref>Replacement secret-vault:// reference to pin (mutually exclusive with the inline channel).
--enabledWhether dispatch resolves sessions through the provider.
--credential-env <name>Environment variable holding the replacement inline credential.
--credential-promptPrompt for the replacement inline credential without echo.

See also​

  • opschain docs cli/admin-transport-providers-create — the custody channels in full.