Skip to content

chore: Migrate gsutil usage to gcloud storage#1834

Merged
a-maurice merged 5 commits intofirebase:mainfrom
gurusai-voleti:ai-gsutil-migration-88c51364d3a44635b8e90c46a09bcab3
Feb 24, 2026
Merged

chore: Migrate gsutil usage to gcloud storage#1834
a-maurice merged 5 commits intofirebase:mainfrom
gurusai-voleti:ai-gsutil-migration-88c51364d3a44635b8e90c46a09bcab3

Conversation

@gurusai-voleti
Copy link
Contributor

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
Copy link
Contributor

Summary of Changes

Hello @gurusai-voleti, 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 migrates all Google Cloud Storage command-line interactions from the legacy gsutil tool to the modern gcloud storage interface. The changes ensure that all GCS operations, including file transfers, directory listings, and content retrieval, leverage the improved performance and consistent authentication offered by gcloud storage. This update is part of a broader effort to standardize GCS tooling and enhance integration with other gcloud components.

Highlights

  • Migration to gcloud storage: All instances of gsutil commands have been replaced with their gcloud storage equivalents across the codebase, aligning with the recommended Google Cloud Storage CLI.
  • Updated GCS operations: File upload, listing, and reading operations that previously used gsutil cp, gsutil ls, and gsutil cat now correctly invoke gcloud storage cp, gcloud storage ls, and gcloud storage cat respectively.
  • Revised documentation and tips: Informational messages and GCS usage tips within the scripts have been updated to guide users towards gcloud storage commands, including changes to recursive copy flags.
  • Tool detection logic: The system now correctly identifies and verifies the presence of the gcloud command-line tool instead of gsutil for GCS interactions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • scripts/gha/gcs_uploader.py
    • Replaced gsutil cp with gcloud storage cp for artifact uploads.
    • Updated usage tips in logging messages to reflect gcloud storage cp syntax, including --recursive.
  • scripts/gha/integration_testing/ftl_gha_validator.py
    • Changed the GSUTIL variable to locate gcloud instead of gsutil.
    • Modified _gcs_list_dir to use gcloud storage ls --recursive instead of gsutil ls -r.
    • Modified _gcs_read_file to use gcloud storage cat instead of gsutil cat.
  • scripts/gha/integration_testing/gcs.py
    • Updated the docstring for relative_path_to_gs_uri to refer to gcloud storage.
    • Revised get_gsutil_tips to provide advice and commands for gcloud storage.
    • Changed the tool version check from gsutil version to gcloud -v.
Activity
  • This pull request was automatically generated by an agent to migrate gsutil usage to gcloud storage.
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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request automatically migrates gsutil commands to gcloud storage. The changes are mostly correct, but there are a few areas for improvement to enhance code clarity and complete the migration. I've left comments regarding misleading variable and function names, and pointed out some redundant and unnecessary code that should be removed to finalize the transition from gsutil.

@a-maurice a-maurice added tests-requested: quick Trigger a quick set of integration tests. skip-release-notes Skip release notes check and removed tests-requested: quick Trigger a quick set of integration tests. labels Feb 24, 2026
Removed gsutil checks from gcloud SDK verification.
@a-maurice a-maurice merged commit cbd6673 into firebase:main Feb 24, 2026
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-release-notes Skip release notes check

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants