Set one tenant config key

Persists a per-tenant override for a fenced config key. Body: {"value":"..."}. The value is scope-fenced + validated against the catalog: a missing value is a schema 422, an empty value a coded 400, an off-catalog key 404, an off-enum / non-bool value 422. RBAC: config:write; the writing actor and the tenant are always derived from the validated request identity, never a path or payload value.

PUT /admin/config/{key}

Set one tenant config key

cURL

curl --request PUT \
  --url https://slc.sandbox.lerian.net/admin/config/{key} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "value": "cd"
}'

200

{
  "key": "connectivity.file_transport",
  "value": "cd"
}

Authorizations

Authorization · string · header · required

JWT bearer token issued by the identity provider.

Path Parameters

key · string · required

Fenced connectivity config key.

Example:

"connectivity.file_transport"

Body

application/json

value · string · required

New value for the fenced config key. Scope-fenced + validated against the connectivity config catalog.

Example:

"cd"

Response

200

application/json

OK

key · string · required

Fenced connectivity config key.

Example:

"connectivity.file_transport"

value · string · required

Effective value for the key: the tenant override when present, else the catalog default.

Example:

"cd"