Apply Defaults
POST/api/v1/system/defaults/apply
Pin the current TTL, common header and merge engine onto the named sources and their tables.
Sources that are not in the list are left alone. A source that already stores these values is unchanged in the deploy repo. A missing or engine-owned name fails the request before any source is written.
A draft takes the values in place. A deployed version is never rewritten: the
values land on a new major version, which becomes current. Either way the
table takes them when that version is deployed.
A named source whose deployed version already carries the values has its table
brought to them in this request: the TTL moves and the header's missing
columns are added. The engine of an existing table needs a rebuild, so it
reaches new tables only, and existing columns keep their type. live
reports each source: what reached the table, what did not and why. A
ClickHouse failure is reported on that source, and the pin stays committed.
A pin production+team sends to review is listed in awaiting_review with
review_required and the review headers, and its table is left alone until
the branch merges, since main still carries the source as it was.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
- default
Successful Response
No valid session: the credentials are missing, invalid or expired, or the account behind them is disabled or blocked
Refused: the session lacks the action this route checks, or its account must replace an issued password first. A SCIM route answers a refused action in the RFC 7644 error envelope
not_found: a named source does not exist
conflict: a named source is engine-owned and cannot be edited
Validation Error
Problem details (RFC 9457)