chore: Migrate gsutil usage to gcloud storage

[gurusai-voleti]

Automated: Migrate {target_path} from gsutil to gcloud storage

This CL is part of the on going effort to migrate from the legacy gsutil tool to the new and improved gcloud storage command-line interface.
gcloud storage is the recommended and modern tool for interacting with Google Cloud Storage, offering better performance, unified authentication, and a more consistent command structure with other gcloud components. 🚀

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.

⚠️ Action Required: Please Review and Test Carefully

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 gsutil and gcloud storage that 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 rsync command has a different file deletion logic than gsutil 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 CLI team 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.com

We appreciate your partnership in this important migration effort!

#gsutil-migration

[gurusai-voleti]

Hi, Can we get your review on this PR? Thanks!

[gemini-code-assist]

Summary of Changes

Hello @gurusai-voleti, I'm Gemini Code Assist¹! 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 automates the update of documentation to replace gsutil commands with their gcloud storage counterparts. This change is part of a strategic initiative to standardize on the gcloud storage CLI, which offers a more integrated and performant experience for interacting with Google Cloud Storage. The primary goal is to ensure that all examples and instructions reflect the recommended and modern approach, while also alerting users to potential behavioral shifts that necessitate careful validation.

Highlights

• Command Migration: Migrates all instances of gsutil commands to their gcloud storage equivalents within the affected documentation files.
• Automated Change: This pull request was automatically generated as part of an ongoing effort to transition from the legacy gsutil tool to the modern gcloud storage command-line interface.
• Improved Tooling: gcloud storage is highlighted as the recommended tool, offering better performance, unified authentication, and a more consistent command structure with other gcloud components.
• Review and Testing Required: Emphasizes the critical need for thorough review and testing of these changes, as gsutil and gcloud storage can have subtle behavioral differences (e.g., rsync deletion logic, command output structure).
• Support Availability: The GCS CLI team is available to provide support, assist with testing, and address any complex use cases or blockers encountered during the migration.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request automatically migrates gsutil commands to their gcloud storage equivalents in two README files. The migrations are syntactically correct. However, I've identified a pre-existing issue in the cleanup steps of both READMEs where the bucket deletion command would fail because not all created resources (specifically, temporary files) are removed. I've provided suggestions to make the cleanup process more robust and ensure it completes successfully.