Add a task dependency
POST/api/v1/tasks/:task_id/dependencies
Makes the task depend on depends_on_task_id, a task in the same project: the path's task is blocked until that one closes, in any terminal state. The pair is the dependency's identity: adding it again answers 200 with the existing one. An edge that would close a cycle is refused.
Request
Responses
- 200
- 201
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
The dependency already held; it is returned unchanged
The dependency
The task names itself (TASK_DEPENDENCY_SELF), depends_on_task_id is missing or in another project (TASK_DEPENDENCY_TARGET_NOT_FOUND), or the body is invalid
Unauthorized
Forbidden
The task does not exist
The task is closed (TASK_DEPENDENCY_CLOSED) or the dependency would close a cycle (TASK_DEPENDENCY_CYCLE, meta.path)
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there