Delete an organization template
Delete a template, every version it holds, every tag that names one and its build records, a running build included. The reply counts the build records it destroyed. That count is the part nothing else records: a build's status, its error and the resources it ran on live in that row alone, and its log stays in storage for seven days with nothing left to address it by. Read stats.builds.total on the template first to see the number before you delete. It is refused with 409 while a sandbox records any of those versions, and the refusal names up to 5 of them and counts the rest. A paused sandbox counts, and so does one whose teardown has not finished. There is no override: delete those sandboxes first. This cannot be undone: archive the template instead to refuse a create from it and keep every version as it is. Requires the organization admin or owner role.
Delete a template, every version it holds, every tag that names one and its build records, a running build included. The reply counts the build records it destroyed. That count is the part nothing else records: a build's status, its error and the resources it ran on live in that row alone, and its log stays in storage for seven days with nothing left to address it by. Read stats.builds.total on the template first to see the number before you delete. It is refused with 409 while a sandbox records any of those versions, and the refusal names up to 5 of them and counts the rest. A paused sandbox counts, and so does one whose teardown has not finished. There is no override: delete those sandboxes first. This cannot be undone: archive the template instead to refuse a create from it and keep every version as it is. Requires the organization admin or owner role.
Authorization
apiKey API key starting with tektona_. Create one at app-dev.tektona.ai under API Keys.
In: header
Path Parameters
Organization name
Template name
length <= 80Response Body
application/json
application/problem+json
curl -X DELETE "https://example.com/v1/orgs/string/templates/string"{ "builds": 12}{ "detail": "Property foo is required but is missing.", "errors": [ { "location": "string", "message": "string", "value": null } ], "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "https://example.com/errors/example"}Create a project template POST
Create a template scoped to the project, referenced as project/<name> or by the bare name. Requires the project admin role.
Delete a project template DELETE
Delete a template, every version it holds, every tag that names one and its build records, a running build included. The reply counts the build records it destroyed. That count is the part nothing else records: a build's status, its error and the resources it ran on live in that row alone, and its log stays in storage for seven days with nothing left to address it by. Read `stats.builds.total` on the template first to see the number before you delete. It is refused with 409 while a sandbox records any of those versions, and the refusal names up to 5 of them and counts the rest. A paused sandbox counts, and so does one whose teardown has not finished. There is no override: delete those sandboxes first. This cannot be undone: archive the template instead to refuse a create from it and keep every version as it is. Requires the project admin role.