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

[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 systematically migrates existing gsutil command-line usages to the recommended gcloud storage tool across the codebase. This automated change aims to standardize interactions with Google Cloud Storage, leveraging the performance benefits, unified authentication, and consistent command structure offered by gcloud storage. The modifications span various scripts and documentation, ensuring that the project aligns with the latest best practices for Google Cloud CLI tools.

Highlights

• Migration to gcloud storage: All instances of gsutil commands in various scripts and documentation have been updated to use the modern gcloud storage command-line interface.
• Command Replacements: Specific gsutil commands like cp, stat, rm, iam ch, ls, kms authorize, and kms encryption have been replaced with their gcloud storage equivalents, such as gcloud storage cp, gcloud storage objects list --stat, gcloud storage rm, gcloud storage buckets add-iam-policy-binding, gcloud storage ls, gcloud storage service-agent --authorize-cmek, and gcloud storage buckets update --default-encryption-key respectively.
• Documentation Updates: Code examples and comments in documentation and test files, particularly those demonstrating hash calculations or bucket setup, have been updated to reflect the use of gcloud storage hash and other new commands.
• Untranslated Commands: A few gsutil commands in documentation, specifically those using the -l flag for location, were noted as untranslatable by the automation due to lack of direct migration guidance for those specific flags.

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 automates the migration from gsutil to gcloud storage across several files. The changes are mostly correct replacements of equivalent commands. However, I've found a few issues. In ci/cloudbuild/builds/rotate-keys.sh, an incorrect gcloud command was generated to replace gsutil stat, which could break the script. In google/cloud/storage/doc/setup-test-resources.md, the automation failed to translate some commands and left comments; these commands were incorrect in the first place, and I've suggested fixing them with the proper gcloud equivalents.

[scotthart]

/gcbrun

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.95%. Comparing base (fa35817) to head (2ba366d).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15910      +/-   ##
==========================================
- Coverage   92.96%   92.95%   -0.01%     
==========================================
  Files        2460     2460              
  Lines      228931   228931              
==========================================
- Hits       212826   212811      -15     
- Misses      16105    16120      +15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[scotthart]

/gcbrun