Update R2 copy script to support cross-bucket copy#14
Merged
ryanking13 merged 1 commit intomainfrom Mar 26, 2026
Merged
Conversation
dom96
approved these changes
Mar 25, 2026
Contributor
dom96
left a comment
There was a problem hiding this comment.
Thank you for finding these and working through them!
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.
I migrated all the python packages files in our prod bucket using #13, but I noticed that we are storing python packages for the package version 20240829.4 in our playground account, not in the prod bucket. They also needs migration.
To migrate those files as well, this PR updates the migration script to support cross-bucket copy.
Test Plan
Tested locally with my personal account:
python packages/copy_r2_bucket.py --src python-package-bucket --dest pyodide-capnp-bin --prefix python-package-bucket --src-prefix "20240829.4"