Trigger or fetch generated node log files

GET 
/data-pipelines/:id/executions/:executionid/nodes/:node_name/logs

Primary integration is v2-downloadLogs. The working GET branch is logs=all (requires servicename=data-pipelines and logtype). It starts log file generation (Message "Triggered log file creation") or returns PresignedURL when a file already exists. Execution must be in a terminal state (LOG-1006). logs=latest is declared in the spec but is not a working GET unless action is also a POST action (view-logs|generate-logs|download-logs), which then expects a POST body. Prefer POST for view/generate/download.

Request

Responses

200

Trigger message or PresignedURL for logs=all.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

400

Invalid input. downloadLogs maps InvalidInputException and UnauthorizedUserException to HTTP 400.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

500

Log retrieval failed (LOG-1007 or other GenericFailureException).

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers