POST /api/operations

Request lifecycle operation#

Private controller API. Call this route through the user’s Unix socket, locally or over SSH. It is not exposed on the server’s public origin.

Listed permission codes are alternatives, not token scopes. The service also checks access to the requested records and rejects stale revisions or controller generations.

HTTP 202 means the request was accepted for processing. Check the operation’s status to find out whether it completed.

• Authentication, envelopes and pagination
• Language-neutral client examples

Path parameters#

empty object; unknown fields rejected

Validation#

check.empty

Referenced definitions:

• empty

Query parameters#

custom validation: none ; see function below

Query parameters are URL text. The validation function below specifies their format, defaults and combinations. Pagination applies only to operations that use it.

Additional checks#

The following checks apply in addition to the field limits.

Constraint on value:

export function none(input: unknown) {
    const parsed = listQuery([])(input);
    return parsed.ok ? success({}) : parsed;
}

Validation#

none

Referenced definitions:

• none

Request body#

object; fields below; unknown fields rejected; constraint: Only an explicit software update supplies its installed release directory ( operationInput )

Additional checks#

The following checks apply in addition to the field limits.

Constraint on object:

value => (value.action === 'update') === (value.releaseDirectory !== undefined)

Constraint on releaseDirectory:

value => value.startsWith('/') && !value.includes('\\')
    && value.split('/').slice(1).every(segment => segment && segment !== '.' && segment !== '..')

Validation#

operationInput

Referenced definitions:

• operationInput

Response data#

object; fields below; unknown fields rejected; constraint: Only an explicit software update supplies its installed release directory ( operationView )

Additional checks#

The following checks apply in addition to the field limits.

Constraint on object:

value => (value.action === 'update') === (value.releaseDirectory !== undefined)

Constraint on releaseDirectory:

value => value.startsWith('/') && !value.includes('\\')
    && value.split('/').slice(1).every(segment => segment && segment !== '.' && segment !== '..')

Constraint on receiptPending:

input => input === true ? success(true) : failure('invalid', 'Only unacknowledged controller requests are pinned')

Validation#

operationView

Referenced definitions:

• operationView

Response envelope#

A successful JSON response contains data and meta. Replace the data placeholder below with the response fields described above. Errors contain error instead of data.

{
  "data": "<value matching the response-data validator>",
  "meta": {
    "requestId": "00000000-0000-0000-0000-000000000001"
  }
}