Create a team
Organization owners and cluster admins (`org.create_team` on `org_id`). A creator who is a member of the organization becomes the team's admin. 409 `name-taken` when the organization has a team of that name.
openapi/harthelm.yaml at v1.5.0__Host-harthelm_session<token>Browser session of the UI (12 h idle, 7 days absolute). State-changing requests also need the header
Harthelm-CSRF: 1 and a matching Origin.
Idempotency-Key?stringClient-chosen key (at most 255 characters); a repeated key returns the first result for 24 h.
1 <= length <= 255application/json- body
org_id*stringuuidname*TenantName1 to 64 characters without leading or trailing spaces; unique case-insensitively.
^\S(.*\S)?$1 <= length <= 64The team.
application/json- response
id*IDNumeric resource id.
int641 <= valueorg_id*stringuuidname*stringrole?TeamRoleThe caller's role; absent when a cluster admin sees a team they are not a member of.
"admin""member"created_at*stringdate-timeallow_run_as_user?booleanContainer services of the team may set runAsUser, root included (a cluster admin sets it with
PATCH /teams/{team}). Absent for an older core.
deleting?booleanThe team is being deleted; it takes no writes. Absent for an older core.
delete_operation_id?stringThe team.delete operation of a deleting team.
uuidpermissions?array<>The caller's permissions on the resource; the UI shows only what they allow. Absent for an older core.
curl -X POST 'https://console.example.com/api/v1/teams' \ -H 'Content-Type: application/json' \ -d '{ "org_id": "a40f5d1f-d889-42e9-94ea-b9b33585fc6b", "name": "string"}'{ "id": 1, "org_id": "a40f5d1f-d889-42e9-94ea-b9b33585fc6b", "name": "string", "role": "admin", "created_at": "2019-08-24T14:15:22Z", "allow_run_as_user": true, "deleting": true, "delete_operation_id": "2a58cc5e-4ba9-418a-8f8b-9007f099696a", "permissions": [ "string" ]}Return the team to the default quota
Cluster admins only (`platform.admin`). Removes the override.
Delete a team
Team admins (`team.manage`). Asynchronous and resumable: the team turns `deleting` at once (it takes no writes, 409 `team-deleting`), and the operation `team.delete` removes its workspaces (purged at once, without the 7-day soft delete), managed services, registries, domains, git access defaults, shared vaults and namespace, then the team with its memberships and invitations. Every member loses access when the deletion starts. Deleting a deleting team returns its operation, or, when that operation failed because a step gave up (problem `team-delete-failed` with `failed_team`), starts a new `team.delete` operation that resumes the cascade.