Skip to main content
Version: v5.7.0

opschain admin transport-providers bindings

packs:rpc

Manage transport-provider scope bindings — the declared scope path → provider mapping that gives a subtree its default transport provider: / binds the estate default, /projects/<code> and /projects/<code>/environments/<code> override it down the node tree, deepest covering scope winning. Dispatch resolves the binding at step build; a node property (rpc.provider_ref) overrides any binding for special cases.

Declaring a binding (set) requires the packs:rpc entitlement; delete is deliberately ungated so a lapsed estate can always unwind. Every write is audited (api:transport_provider_bindings:*).

SubcommandPurpose
listEvery declared binding with its provider's enabled state and health.
set <scope-path>Declare (or re-point) the binding for a scope path.
delete <scope-path>Remove the binding (the scope falls back to the default).
resolve <node-path>Which provider serves the node path, and which scope decided.

See also​

  • opschain docs cli/admin-transport-providers — the catalog bindings point at.
  • opschain docs cli/admin-transport-grants — who may use the bound providers.