-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[GH-1402] Write Workflow Outputs to the Terra Data Repository (#474)
* [GH-1405] Add Schema for TerraDataRepoSink (#473) [GH-1405] Add Schema for TerraDataRepoSink RR: https://broadinstitute.atlassian.net/browse/GH-1405 Add schemas for the following types - TDRJobStatus - TDRJobType - TerraDataRepoSinkDetails and the TerraDataRepoSink table. * [GH-1314] Start Implementing DataRepo Sink (#476) RR: https://broadinstitute.atlassian.net/browse/GH-1413 Add load/create functions for the data repo sink - leaving update as "unimplemented". * [GH-1415] Implement `update-sink` for TerraDataRepoSink (#478) RR: https://broadinstitute.atlassian.net/browse/GH-1415 This change contains a rough implementation of the TerraDataRepo sink update functionality. After discovering certain hurdles in the original design, I've made some tweaks and incorporated TDR's work https://broadworkbench.atlassian.net/browse/DR-1960 so that we only need one ingest request instead of separately loading the output files and output metadata. At the time of writing, DR-1960 is work in progress so our ingests won't work just yet. Some things to call out in this change that I'm deferring to a follow up change into the feature branch: I need to upload the json file for TDR to ingest. I'm currently using our test outputs bucket as a temporary folder for this which is obviously not a production-ready solution. Possible fixes include creating a scratch bucket for workflow-launcher, creating a bucket per workload, using the executor's execution bucket... etc. Suggestions welcome. Since the ingests always fail, I'm leaving some of the work post-ingest as a TODO. * [GH-1425] Expose `TerraDataRepoSink` Via the HTTP API (#484) RR: https://broadinstitute.atlassian.net/browse/GH-1425 Add specs and register in wfl.api/spec. Add end-to-end system test for reading/writing workflow inputs/outputs to TDR (used the illumina_genotyping_array pipeline as it's smaller than sarscov2_illumina_full). Co-authored-by: Chengchen(Rex) Wang <14366016+rexwangcc@users.noreply.github.com> * [GH-1416] Document DataRepo Sink (#485) RR: https://broadinstitute.atlassian.net/browse/GH-1416 Add section to `sink.md` describing how to configure workflow-launcher to write outputs back to a terra datarepo dataset. * [GH-1430] Remove `stage/validate-or-throw` and inline their implementations into `create-X`. (#490) RR: https://broadinstitute.atlassian.net/browse/GH-1430 Remove stage/validate-or-throw and inline their implementations in their respective create-X functions. This is done because - we were losing context (ie. was this a source/sink/executor) and had a collision in the tdr sink and source impls - these multimethods didn't really make sense and require some redesign work * address @okotsopoulos's feedback Co-authored-by: Chengchen(Rex) Wang <14366016+rexwangcc@users.noreply.github.com>
- Loading branch information
Showing
37 changed files
with
1,160 additions
and
447 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.