Update Draft Config

Replace or publish a draft

Use the supported synchronous database from the catalog server. This updates a stored draft; scoped ownership still applies, even when the component is readable by other users.

Send a complete replacement config object: it is not deep-merged with the old configuration. For example, with latest version 2:

{"config":{"name":"Revised Agent"},"guard":{"latest_version":2}}

Only guard.latest_version is accepted here. A stale expected version returns 409; a non-null guard.current_version returns 400.

Setting stage="published" promotes the draft and makes it current. Published configurations are immutable through this endpoint; further edits return 400. Create another draft version to make subsequent changes.

PATCH/components/{component_id}/configs/{version}

Update an existing draft config. Cannot update published configs.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Path Parameters

component_id*Component Id

Component ID

version*Version

Version number

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Config fields to update

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl --request PATCH 'https://example.com/components/string/configs/0' \  --header 'Content-Type: application/json' \  --data-raw '{}'
{  "component_id": "string",  "version": 0,  "label": "string",  "stage": "string",  "config": {},  "notes": "string",  "created_at": 0,  "updated_at": 0}