Orchestrations

Update Orchestration Secrets

PATCH/v2/orchestrations/{orchestration_id}/secrets

Apply ``remove`` then ``set`` to the orchestration's map. Incremental rather than whole-replace because no caller can read the current values back, so none of them can construct a full map. The gates mirror the agent-level secrets write one for one — this is the same authority over what lands in a sandbox's environment, just aimed at every member at once — with the group gate in front and the kill switch last, so a caller who would have been rejected anyway learns nothing about the deployment's configuration.

Path Parameters

orchestration_idstring · uuidrequired

Request Body

setobjectoptional

removearray<string>optional

Request

curl --request PATCH \
  --url https://api.brainbaselabs.com/v2/orchestrations/{orchestration_id}/secrets \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "set": {
    "property1": "string",
    "property2": "string"
  },
  "remove": [
    "string"
  ]
}'

Response

json

{
  "keys": [
    "string"
  ],
  "enabled": true,
  "updated_at": "2019-08-24T14:15:22Z"
}