Read or follow a task's log
Without follow: the stored log bytes from the offset from (default 0), as application/octet-stream, with X-Ezgh-Log-Next: the offset to read from next. An offset past the end is an empty answer, never an error. With follow=true: server-sent events. Each data event's id is the offset after it and its data is base64 of at most 49,152 log bytes; a comment is sent every 15 seconds; an end event (data {"status": the task's status}) once the task is finished and its log is sent, at once for a finished task. A stream lasts at most 890 seconds and then closes without end: reconnect with from set to the last id. Last-Event-ID is never read. A log is kept up to 16 MiB, then a marker line. Recorded in Trails only when refused.
https://build.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/pipelines/{pipeline}/tasks/{task}/logAuthorization
Path parameters
Query parameters
Returns
200
The log's bytes from the offset, or with follow=true a stream of server-sent events: data, heartbeat comments, then end.
string400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.