-
Notifications
You must be signed in to change notification settings - Fork 8
Remove unused embargo buckets #249
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
Conversation
23f99dd to
5e08f19
Compare
|
I'll rebase this to include changes from #248 . |
9dfb77d to
a756642
Compare
5f0847a to
ffacf9d
Compare
ffacf9d to
455c222
Compare
|
@sandyhider @NEStock I don't think EMBER ever made use of these buckets - these "embargo buckets" were previously used for embargoed data prior to a redesign where we consolidated all data into one bucket. I believe EMBER started after we did that switch, so I would expect these buckets to be empty. If they are not empty, they should be emptied prior to doing a terraform apply of this PR to avoid errors. |
@mvandenburgh Thanks for the heads up! I believe we are not currently using them, but we will definitely double check |
|
I agree with Nicole. We looked into using them for a while with Private data but scrapped that plan. |
🚨 Setting this as draft until we are ready to delete the buckets, do not merge yet.
Removes the old embargo buckets that were used before the embargo redesign. Not having to support these buckets allows significant simplication of the
dandiset_bucketmodule.Fixes #210