Migrate gsutil usage to gcloud storage #13729
Conversation
|
Hi @glasnt, Can we get your review on this PR? Thanks! |
product-auto-label
bot
added
samples
Summary of ChangesHello @bhandarivijay-png, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request systematically updates existing Google Cloud Storage command-line operations from the deprecated Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request automatically migrates gsutil commands to gcloud storage in the Django sample's end-to-end test configuration files. The migration of the bucket creation command is correct. However, I've identified an issue with the cleanup step. The migrated command for deleting the storage bucket only empties it, but doesn't delete the bucket itself, which could lead to resource leaks. I've provided a suggestion to ensure the bucket is fully deleted. Please review the suggested change.
| ./retry.sh "gsutil ls gs://${_STORAGE_BUCKET}" \ | ||
| "gsutil -m rm -r gs://${_STORAGE_BUCKET}" | ||
| ./retry.sh "gcloud storage ls gs://${_STORAGE_BUCKET}" \ | ||
| "gcloud storage rm --recursive gs://${_STORAGE_BUCKET}" |
There was a problem hiding this comment.
The migrated command gcloud storage rm --recursive gs://${_STORAGE_BUCKET} only deletes the contents of the bucket, not the bucket itself. The original gsutil rm -r command was likely incorrect as it would fail when used on a bucket URI. While this change fixes the command execution error, it doesn't complete the cleanup, leaving an empty bucket behind. To prevent resource leaks, the bucket itself should be deleted. I suggest chaining the bucket deletion command after emptying it. Using /** ensures all object versions are deleted, which is important if versioning is enabled on the bucket.
"gcloud storage rm --recursive gs://${_STORAGE_BUCKET}/** && gcloud storage buckets delete gs://${_STORAGE_BUCKET}"
glasnt
added
the
kokoro:force-run
kokoro-team
removed
the
kokoro:force-run
3 participants
Automated: Migrate {target_path} from gsutil to gcloud storage
This CL is part of the on going effort to migrate from the legacy
gsutiltool to the new and improvedgcloud storagecommand-line interface.gcloud storageis the recommended and modern tool for interacting with Google Cloud Storage, offering better performance, unified authentication, and a more consistent command structure with othergcloudcomponents. 🚀Automation Details
This change was generated automatically by an agent that targets users of
gsutil.The transformations applied are based on the gsutil to gcloud storage migration guide.
While we have based the automation on the migration guide, every use case is unique.
It is crucial that you thoroughly test these changes in environments appropriate to your use-case before merging.
Be aware of potential differences between
gsutilandgcloud storagethat could impact your workflows.For instance, the structure of command output may have changed, requiring updates to any scripts that parse it. Similarly, command behavior can differ subtly; the
gcloud storage rsynccommand has a different file deletion logic thangsutil rsync, which could lead to unintended file deletions.Our migration guides can help guide you through a list of mappings and some notable differences between the two tools.
Standard presubmit tests are run as part of this CL's workflow. If you need to target an additional test workflow or require assistance with testing, please let us know.
Please verify that all your Cloud Storage operations continue to work as expected to avoid any potential disruptions in production.
Support and Collaboration
The
GCS CLIteam is here to help! If you encounter any issues, have a complex use case that this automated change doesn't cover, or face any other blockers, please don't hesitate to reach out.We are happy to work with you to test and adjust these changes as needed.
Contact:
gcs-cli-hyd@google.comWe appreciate your partnership in this important migration effort!
#gsutil-migration