Chelabase
ManagementKeys

Rotate a key

POST
/v1/databases/{id}/branches/{branch_id}/keys/{key_id}/rotate

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Database id

Formatuuid
branch_id*string

Branch id

Formatuuid
key_id*string

Key id

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/databases/497f6eca-6276-4993-bfeb-53cbbbba6f08/branches/497f6eca-6276-4993-bfeb-53cbbbba6f08/keys/497f6eca-6276-4993-bfeb-53cbbbba6f08/rotate"
{  "databases": [    "string"  ],  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",  "key": "string",  "kind": "public",  "name": "string",  "prefix": "string",  "role": "string"}

Revoke a secret key DELETE

Previous Page

Start a schema merge between a branch and its parent POST

`into_parent` merges the branch's schema changes into its parent; `from_parent` brings the parent's changes into the branch. Both branches must be ready and `normal`; main has no parent. The merge starts as `computing`: the worker reads both schemas and the branch point and fills in the analysis and the plan (poll `getMerge` until it is a `draft`). `database` is the Postgres database to merge (the branch's main one when omitted). One merge per pair and Postgres database can be open at a time.