The JSON Schema of harthelm.yml
`schemas/harthelm.schema.json` (draft 2020-12, schema `harthelm/v1`), served from the binary so editors and code-server's YAML extension never fetch it from the internet. Works without credentials.
openapi/harthelm.yaml at v1.5.0The schema.
application/schema+json- response
[key: string]?anycurl -X GET 'https://console.example.com/api/v1/schemas/harthelm.json'{ "$id": "urn:harthelm:schema:harthelm-v1", "title": "harthelm.yml", "type": "object", "required": [ "schema" ], "properties": { "schema": { "const": "harthelm/v1" } }}Change a team's settings
`name` needs `team.manage` (409 `name-taken`, audited as `team.update`). `allow_run_as_user` is for cluster admins only: it lets the team's container services set `runAsUser`, root included; while it is on, the team's namespace enforces Pod Security `baseline` instead of `restricted`. Without it, every workspace pod runs as the UID that owns its volume and a Plan that sets `runAsUser` has the blocker `run-as-not-allowed`. Audited as `team.settings`. A deleting team answers 409 `team-deleting`.
This API's OpenAPI document
This document as built into the binary; the API reference at `/api/docs` (Scalar, bundled, outside `/api/v1`) reads it from here. Works without credentials. The `ETag` is the quoted SHA-256 of the document; send it back in `If-None-Match` to get `304` while the server still implements the same document.