Description
The WES specification defines [TaskLog](https://github.com/ga4gh/workflow-execution-service-schemas/blob/03c795c0cd890b1b8735f7ad27e546008a007cf2/openapi/workflow_execution_service.openapi.yaml#L909-L935), which can optionally be exposed via TES URIs.
From the perspective of a WES implementor, it would be valuable if the nf-ga4gh plugin could:
- Launch tasks against TES while exposing their corresponding IDs,
- Allow WES to parse these and construct
TaskLog responses appropriately.
Rationale
This would enable better interoperability between Nextflow (via TES) and WES by making task-level logs and IDs available in a standard-compliant way.
Even a simple log.trace with task IDs would be sufficient for WES implementations to build a proper response.
Description
The WES specification defines [TaskLog](https://github.com/ga4gh/workflow-execution-service-schemas/blob/03c795c0cd890b1b8735f7ad27e546008a007cf2/openapi/workflow_execution_service.openapi.yaml#L909-L935), which can optionally be exposed via TES URIs.
From the perspective of a WES implementor, it would be valuable if the nf-ga4gh plugin could:
TaskLogresponses appropriately.Rationale
This would enable better interoperability between Nextflow (via TES) and WES by making task-level logs and IDs available in a standard-compliant way.
Even a simple
log.tracewith task IDs would be sufficient for WES implementations to build a proper response.