-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add optional transfer step to dataset DAG #259
Conversation
3326f46
to
389aa9a
Compare
Rebased on dev to incorporate recent dataset DAG changes - needs testing + re-review. |
…control flow) - also modified sm2a makefile to run on ubuntu
0d13062
to
ff49699
Compare
config = { | ||
**payload, | ||
**ti.dag_run.conf, | ||
"origin_bucket": payload.get("bucket", ti.dag_run.conf.get("origin_bucket", "veda-data-store")), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should the origin here be veda-data-store-staging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessarily, doing it this way allows us to promote/transfer datasets where assets are stored in other buckets (I was thinking of some of the COVID dashboard collections here, but there could be others)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested the changes locally and it seems to be working.
Addresses #256
If
transfer: true
is included in the dataset DAG payload, assets will be transferred to the production bucket prior to discovery and STAC item creation.dry_run
is set to True by default - this should be changed before merging, but is better for testing.