Sniffing for and workaround for keeping output of croo workflows #5096
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is on top of #5095 and additionally fixes #5093.
Changelog Entry
To be copied to the draft changelog by merger:
toil-wdl-runner
now correctly finds and returns outputs from tasks in scatters and conditionals when a WDL workflow lacks anoutput
section.toil-wdl-runner
has a new--allCallOutputs
option to allow including all calls' outputs in a workflow's output.toil-wdl-runner
can now detect and try not to delete the outputs of a workflow that is meant to use the Cromwell Output Organizer (croo
). Note thatcroo
still can't actually work on the output oftoil-wdl-runner
.Reviewer Checklist
issues/XXXX-fix-the-thing
in the Toil repo, or from an external repo.camelCase
that want to be insnake_case
.docs/running/{cliOptions,cwl,wdl}.rst
Merger Checklist