Arvados

Showing these would be helpful:

baseCommand: [bwa, mem]
arguments: - {prefix: -t, valueFrom: $(runtime.cores)} - {prefix: -R, valueFrom: "@RG\tID:$(inputs.group_id)\tPL:$(inputs.PL)\tSM:$(inputs.sample_id)"}

(baseCommand before arguments)

hints: - {class: DockerRequirement, dockerImageId: biodckr/bwa, dockerPull: biodckr/bwa}

The DockerImageId should link to the collection of the docker image.

inputs:

outputs: if possible

Branch 10112-workflow-show @ 4c1d34e

Using the partial show_text_with_locators (from #10645), displays baseCommand, arguments, hints, inputs, outputs in workflow Definition tab.

Test run @ https://ci.curoverse.com/job/developer-run-tests/281/

A couple comments:

• DockerImageId is not being rendered as a collection link as suggested on note-7, is this possible?
• Will the workflow definition have additional data that we would like to show? Maybe we can have a generic way of showing the YAML so that the partial doesn’t need to be updated when using a wf_def with new fields?

DockerImageId is not being rendered as a collection link as suggested on note-7, is this possible?

Peter said it is quite involved and for now we just display the text

Will the workflow definition have additional data that we would like to show? Maybe we can have a generic way of showing the YAML so that the partial doesn’t need to be updated when using a wf_def with new fields?

For now this would do as Bryan suggested. Other fields may or may not fit the same display strategy (for example, uuids etc).

Great, this LGTM.

Preload collections @ a7bd5fa