Skip to content

Conversation

@mvandenburgh
Copy link
Member

@mvandenburgh mvandenburgh commented Oct 2, 2025

🚨 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_bucket module.

Fixes #210

@mvandenburgh mvandenburgh self-assigned this Oct 2, 2025
@mvandenburgh
Copy link
Member Author

I'll rebase this to include changes from #248 .

@mvandenburgh mvandenburgh force-pushed the rm-embargo-buckets branch 2 times, most recently from 9dfb77d to a756642 Compare October 7, 2025 19:37
@mvandenburgh mvandenburgh force-pushed the rm-embargo-buckets branch 2 times, most recently from 5f0847a to ffacf9d Compare October 24, 2025 14:38
@mvandenburgh mvandenburgh marked this pull request as ready for review October 24, 2025 17:34
@mvandenburgh mvandenburgh merged commit 0e31d6d into master Oct 24, 2025
2 checks passed
@mvandenburgh mvandenburgh deleted the rm-embargo-buckets branch October 24, 2025 17:34
@mvandenburgh
Copy link
Member Author

@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.

@NEStock
Copy link

NEStock commented Oct 27, 2025

@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

@sandyhider
Copy link

I agree with Nicole. We looked into using them for a while with Private data but scrapped that plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove dandiarchive-embargo bucket

5 participants