Instance policy#

PropertyValue
Servicecrossfire
Operationpolicy
MethodGET
Path/api/instance-policy
Authenticationhuman
Success status200
Response dataUnpaginated value
Request formatjson
Maximum request body2097152 bytes (service default)
Permission codesprincipal.read

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

Path parameters#

empty object; unknown fields rejected

Validation#

check.empty

Referenced definitions:

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#

query.none

Referenced definitions:

Request body#

empty object; unknown fields rejected

Validation#

check.empty

Referenced definitions:

Response data#

object; fields below; unknown fields rejected ( policy )

Field pathRepresentation and constraints
revisionexact JSON integer; 0…9007199254740991
maxOwnerAgentsexact JSON integer; 1…100
maxAgentsexact JSON integer; 1…1000
maxMessageBytesexact JSON integer; 4096…4194304
fleetIdleTimeoutSecondsexact JSON integer; 0…604800
maxPendingexact JSON integer; 1…1000
enrollmentSecondsexact JSON integer; 60…3600
reconcileSecondsexact JSON integer; 30…3600
agentInstructionswell-formed plain text; maximum 8192 UTF-8 bytes
signupModeinvitation or open
invitationIssuersadministrators or members

Validation#

res.policy

Referenced definitions:

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"
  }
}