Repository navigation
orchestration: describe the input and data buckets of the staging DAGs - #224
Closed
project-defiant wants to merge 1 commit into
Closed
project-defiant wants to merge 1 commit into
project-defiant wants to merge 1 commit into
Conversation
A draft of how the staging DAGs use Google Cloud Storage: input buckets for data downloaded from the sources, data buckets with a dated folder per run (config/, bin/, output/), prod and test environments, fixtures for test runs, and cache for large or incremental data. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or 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
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.
Summary
A draft description of how the staging DAGs use Google Cloud Storage, kept as a draft until the conventions settle:
<env>/<run_ts>/{config,bin,output}, inprodandtestfixtures/: slices of the inputs used by test runscache/: large or incremental data reused across runsThe page is
orchestration/docs/datasources/README.md, linked fromorchestration/docs/README.md.It describes the layout that #220 introduced for
gs://gwas_catalog_top_hits, and that #221 (StagingDagConfig) writes.Open points
cache/.🤖 Generated with Claude Code