opschain admin secrets bindings set
secrets:multi-vault
Declares (or re-points) the binding for a scope path: from then on,
unprefixed secret-vault:// references under that scope resolve through
the named provider, and leased steps under it are minted from that
provider. The scope path is / (the estate default),
/projects/<code> or /projects/<code>/environments/<code>; the provider
must be enabled (a binding to a disabled provider would refuse every
resolution under its scope). Requires the secrets:multi-vault
entitlement; audited as
api:secrets_provider_bindings:create (or :update when re-pointing).
opschain admin secrets bindings set /projects/payments --provider payments
Bound /projects/payments to provider "payments"
Flags
| Flag | Meaning |
|---|---|
--provider <code-or-id> | The provider the scope binds to (required; must be enabled). |
--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-delete— remove a binding.