Problem:
We want to be able to add user generated labels to workflow task logs. If labels are supported, we can better track resources and this will allow users to easily delineate and organize repeated runs of their workflows.
Solution:
CoA user provides json file with key-value pairs (for example labels describing experiment such as sample_name, dataset_name, etc), this json file is passed to Cromwell API.
To do:
TES backend to copy labels to tags in TES object – TES changes, owner: Broad
Trigger service to handle labels.json - Trigger Service changes, owner: MSFT
Describe alternatives you've considered
Created fake runtime attributes and inputs, that requires wdl changes and won't be used by general audience.
Additional context
Cromwell has an optional parameter ‘labels’ to specify a file of JSON key-value label pairs to associate with the workflow (see Submit a workflow for execution at https://cromwell.readthedocs.io/en/stable/api/RESTAPI/). At the moment Trigger Service doesn’t handle labels.json.
Problem: We want to be able to add user generated labels to workflow task logs. If labels are supported, we can better track resources and this will allow users to easily delineate and organize repeated runs of their workflows.
Solution: CoA user provides json file with key-value pairs (for example labels describing experiment such as sample_name, dataset_name, etc), this json file is passed to Cromwell API.
To do:
Describe alternatives you've considered Created fake runtime attributes and inputs, that requires wdl changes and won't be used by general audience.
Additional context Cromwell has an optional parameter ‘labels’ to specify a file of JSON key-value label pairs to associate with the workflow (see Submit a workflow for execution at https://cromwell.readthedocs.io/en/stable/api/RESTAPI/). At the moment Trigger Service doesn’t handle labels.json.