Get the Tenant's artifact limits
managementKeyAuthorizationBearer <token>A management key of the Tenant (role management): it reaches the Management API (/v1/tenant/*) and /v1/me, as itself, never for a subject. Issued only on the Tenant's machine (nylorun-operate keys put <id> --role management) or from NYLORUN_MANAGEMENT_KEY_FILE. Never accepted from a browser (Origin).
Nylorun-Protocol*stringThe protocol version, 18
The limits in force and the bytes used
application/json- response
limits*usedBytes*integer0 <= valueimport { createAdmin } from "@nylorun/admin";const admin = createAdmin();const artifacts = await admin.settings.artifacts.get();{ "limits": { "fileBytes": 0, "totalBytes": 0 }, "usedBytes": 0}Set the Tenant's Agent compute settings PUT
Replaces the Tenant's settings (Tenant setting `environments.config`): the limits every Agent's runtime must fit, the pods' stop grace, the images that carry the engine (`engine.images`) and where harnesses may run. A setting left out takes its default. Answers like `GET`: `config` is the Tenant's settings as stored: only what it set, in exactly the shape `PUT` takes, so a client changes one setting by putting `config` back with that change. `effective` is the configuration in force: `config` with every default filled in, sizes in MiB (`memoryMiB`).
Set the Tenant's artifact limits PUT
The largest file one upload may store, and the most bytes all artifacts may hold. Unset limits take the defaults (100 MiB and 10 GiB).