Chelabase
ManagementMerges

List a database's merges

GET
/v1/databases/{id}/merges

History and open merges, newest first, without their analysis and plan (read one with getMerge).

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Database id

Formatuuid

Query Parameters

branch?string

Only the merges where this branch is the source or the target

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/databases/497f6eca-6276-4993-bfeb-53cbbbba6f08/merges"
[  {    "created_at": "2019-08-24T14:15:22Z",    "created_by": "string",    "database": "string",    "direction": "into_parent",    "error": "string",    "failed_phase": "string",    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "rebaselined": true,    "source_branch_id": "345f76de-8f9d-4a8f-b08e-a28a3db17483",    "status": "computing",    "target_branch_id": "2a8880d3-8c08-4fef-81e0-ec9d6c6def29",    "updated_at": "2019-08-24T14:15:22Z",    "version": 0  }]

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.

Read a merge GET

The merge with its analysis (every changed object, the conflicts with base, target and source side by side), the plan, the last rehearsal, the result and the log. Poll it while the status is `computing`, `rehearsing`, `applying`, `online` or `finishing`, and while a requested after-merge choice is pending (`result.after.requested` or `started`).