[GH-1022] make wgs use CromwellWorkflow table.
#204
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ehigham
force-pushed
the
ehigham/GH-1022-wgs-workload
branch
from
f472e2a
to
63a93aa
Compare
ehigham
force-pushed
the
ehigham/GH-1022-wgs-workload
branch
from
63a93aa
to
c46dccd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
In this change, I'm making the wgs workload store its workflow data in the new (repurposed)
CromwellWorkflowtable .I've implemented the loader such that it's backwards compatible with our current deployments- we can load old WGS workflows as well as new ones (added tests).
I'm pretty sure that wgs now accepts
input_bams as well asinput_crams now. I'll add a test to verify this.