Migrate gsutil usage to gcloud storage #4327

googlyrahman · 2025-10-17T11:57:35Z

Automated: Migrate paths 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!

cc: @sushantkhanna

gemini-code-assist · 2025-10-17T11:58:05Z

Summary of Changes

Hello @googlyrahman, 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 implements an automated migration of Google Cloud Storage command-line interactions from the legacy gsutil tool to the recommended gcloud storage interface across several Jupyter notebooks. This update aims to leverage the enhanced performance, unified authentication, and consistent command structure offered by gcloud storage. While the changes are automated, it is crucial for reviewers to carefully test the updated notebooks, especially given potential subtle behavioral differences between the two tools, particularly concerning IAM policy management and specific file operations.

Highlights

Automated gsutil to gcloud storage Migration: All instances of gsutil commands within Jupyter notebooks have been automatically updated to use the modern gcloud storage command-line interface.
Command Equivalency Updates: Key gsutil operations such as bucket creation (mb), listing objects (ls), copying data (cp), deleting resources (rm), and reading file content (cat) have been replaced with their respective gcloud storage commands.
Complex IAM Policy Migration: gsutil iam ch commands, which modify IAM policies, have been replaced with gcloud storage buckets add-iam-policy-binding commands, accompanied by comments noting the more complex nature of iam ch migration.
Identified Manual Review for gsutil copy: One specific gsutil copy command was flagged with a TODO comment, indicating that a direct equivalent in the gcloud storage migration guide was not found, requiring manual review.

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.

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. ↩

googlyrahman · 2025-10-17T11:58:22Z

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

gemini-code-assist

Code Review

This pull request contains an automated migration from gsutil to gcloud storage. Overall, the migration looks good, but there are a few areas that need attention. I've identified an incorrect migration of gsutil copy which was replaced by a TODO comment instead of the correct gcloud storage cp command. Additionally, there are several instances where the migration of gsutil iam ch to gcloud storage buckets add-iam-policy-binding has resulted in inconsistent quoting for --member and --role arguments. I've added specific comments and suggestions to address these issues for improved robustness and correctness.

gemini-code-assist · 2025-10-17T12:00:56Z

...books/official/model_monitoring_v2/model_monitoring_for_custom_model_online_prediction.ipynb

        "\n",
-        "! gsutil copy $PUBLIC_TRAINING_DATASET $TRAINING_URI\n",
-        "\n",
+        "# TODO: Command \"gsutil copy\" not found in migration guide. Manual review required.\n",        "\n",


The gsutil copy command was not migrated correctly. It should be replaced with gcloud storage cp, as copy is an alias for cp in gsutil.

! gcloud storage cp $PUBLIC_TRAINING_DATASET $TRAINING_URI\n

gemini-code-assist · 2025-10-17T12:00:56Z

notebooks/community/model_evaluation/automl_tabular_classification_model_evaluation.ipynb

-        "! gsutil iam ch serviceAccount:{SERVICE_ACCOUNT}:roles/storage.objectViewer $BUCKET_URI"
-      ]
+        # Note: Migrating scripts using gsutil iam ch is more complex than get or set. You need to replace the single iam ch command with a series of gcloud storage bucket add-iam-policy-binding and/or gcloud storage bucket remove-iam-policy-binding commands, or replicate the read-modify-write loop.
+        "! gcloud storage buckets add-iam-policy-binding $BUCKET_URI --member=serviceAccount:{SERVICE_ACCOUNT} --role=roles/storage.objectViewer"      ]


For consistency with the command on line 628 and to prevent potential shell parsing issues, it's recommended to quote the values for the --member and --role arguments.

! gcloud storage buckets add-iam-policy-binding $BUCKET_URI --member=\"serviceAccount:{SERVICE_ACCOUNT}\" --role=\"roles/storage.objectViewer\"

gemini-code-assist · 2025-10-17T12:00:56Z

notebooks/community/model_garden/model_garden_pytorch_qwen2_5_finetuning.ipynb

        "# Provision permissions to the SERVICE_ACCOUNT with the GCS bucket\n",
-        "! gsutil iam ch serviceAccount:{SERVICE_ACCOUNT}:roles/storage.admin $BUCKET_NAME\n",
-        "\n",
+        "! gcloud storage buckets add-iam-policy-binding $BUCKET_NAME --member=serviceAccount:{SERVICE_ACCOUNT} --role=roles/storage.admin\n",        "\n",


It's a good practice to quote the values for --member and --role to avoid potential shell expansion issues and ensure the command is robust.

! gcloud storage buckets add-iam-policy-binding $BUCKET_NAME --member=\"serviceAccount:{SERVICE_ACCOUNT}\" --role=\"roles/storage.admin\"\n

gemini-code-assist · 2025-10-17T12:00:56Z

.../community/pipelines/google_cloud_pipeline_components_bqml_pipeline_demand_forecasting.ipynb

      "source": [
-        "! gsutil iam ch serviceAccount:{SERVICE_ACCOUNT}:roles/storage.objectCreator {BUCKET_URI}\n",
+        "# Note: Migrating scripts using gsutil iam ch is more complex than get or set. You need to replace the single iam ch command with a series of gcloud storage bucket add-iam-policy-binding and/or gcloud storage bucket remove-iam-policy-binding commands, or replicate the read-modify-write loop.\n",
+        "! gcloud storage buckets add-iam-policy-binding {BUCKET_URI} --member=serviceAccount:{SERVICE_ACCOUNT} --role=roles/storage.objectCreator\n",


For robustness, it's recommended to quote the values for --member and --role arguments to prevent potential shell parsing issues.

! gcloud storage buckets add-iam-policy-binding {BUCKET_URI} --member=\"serviceAccount:{SERVICE_ACCOUNT}\" --role=\"roles/storage.objectCreator\"\n

gemini-code-assist · 2025-10-17T12:00:57Z

.../community/pipelines/google_cloud_pipeline_components_bqml_pipeline_demand_forecasting.ipynb

        "\n",
-        "! gsutil iam ch serviceAccount:{SERVICE_ACCOUNT}:roles/storage.objectViewer {BUCKET_URI}"
-      ]
+        "! gcloud storage buckets add-iam-policy-binding {BUCKET_URI} --member=serviceAccount:{SERVICE_ACCOUNT} --role=roles/storage.objectViewer"      ]


For robustness and consistency, it's recommended to quote the values for --member and --role arguments to prevent potential shell parsing issues.

! gcloud storage buckets add-iam-policy-binding {BUCKET_URI} --member=\"serviceAccount:{SERVICE_ACCOUNT}\" --role=\"roles/storage.objectViewer\"

gemini-code-assist · 2025-10-17T12:00:57Z

notebooks/official/pipelines/google_cloud_pipeline_components_bqml_text.ipynb

-        "! gsutil iam ch serviceAccount:{SERVICE_ACCOUNT}:roles/storage.objectViewer $BUCKET_URI"
-      ]
+        "# Note: Migrating scripts using gsutil iam ch is more complex than get or set. You need to replace the single iam ch command with a series of gcloud storage bucket add-iam-policy-binding and/or gcloud storage bucket remove-iam-policy-binding commands, or replicate the read-modify-write loop.\n",
+        "! gcloud storage buckets add-iam-policy-binding $BUCKET_URI --member=serviceAccount:{SERVICE_ACCOUNT} --role=roles/storage.objectCreator\n",        "\n",


It's recommended to quote the values for --member and --role arguments for robustness and to prevent potential shell parsing issues.

! gcloud storage buckets add-iam-policy-binding $BUCKET_URI --member=\"serviceAccount:{SERVICE_ACCOUNT}\" --role=\"roles/storage.objectCreator\"\n

gemini-code-assist · 2025-10-17T12:00:57Z

notebooks/official/pipelines/google_cloud_pipeline_components_bqml_text.ipynb

+        "# Note: Migrating scripts using gsutil iam ch is more complex than get or set. You need to replace the single iam ch command with a series of gcloud storage bucket add-iam-policy-binding and/or gcloud storage bucket remove-iam-policy-binding commands, or replicate the read-modify-write loop.\n",
+        "! gcloud storage buckets add-iam-policy-binding $BUCKET_URI --member=serviceAccount:{SERVICE_ACCOUNT} --role=roles/storage.objectCreator\n",        "\n",
+        # Note: Migrating scripts using gsutil iam ch is more complex than get or set. You need to replace the single iam ch command with a series of gcloud storage bucket add-iam-policy-binding and/or gcloud storage bucket remove-iam-policy-binding commands, or replicate the read-modify-write loop.
+        "! gcloud storage buckets add-iam-policy-binding $BUCKET_URI --member=serviceAccount:{SERVICE_ACCOUNT} --role=roles/storage.objectViewer"      ]


For robustness and consistency, it's recommended to quote the values for --member and --role arguments to prevent potential shell parsing issues.

! gcloud storage buckets add-iam-policy-binding $BUCKET_URI --member=\"serviceAccount:{SERVICE_ACCOUNT}\" --role=\"roles/storage.objectViewer\"

Migrate gsutil usage to gcloud storage

572ccb3

googlyrahman requested a review from a team as a code owner October 17, 2025 11:57

gemini-code-assist bot reviewed Oct 17, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Migrate gsutil usage to gcloud storage #4327

Migrate gsutil usage to gcloud storage #4327

Uh oh!

googlyrahman commented Oct 17, 2025

Uh oh!

gemini-code-assist bot commented Oct 17, 2025

Uh oh!

googlyrahman commented Oct 17, 2025

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Oct 17, 2025

Uh oh!

gemini-code-assist bot Oct 17, 2025

Uh oh!

gemini-code-assist bot Oct 17, 2025

Uh oh!

gemini-code-assist bot Oct 17, 2025

Uh oh!

gemini-code-assist bot Oct 17, 2025

Uh oh!

gemini-code-assist bot Oct 17, 2025

Uh oh!

gemini-code-assist bot Oct 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Migrate gsutil usage to gcloud storage #4327

Are you sure you want to change the base?

Migrate gsutil usage to gcloud storage #4327

Uh oh!

Conversation

googlyrahman commented Oct 17, 2025

Automation Details

⚠️ Action Required: Please Review and Test Carefully

Support and Collaboration

Uh oh!

gemini-code-assist bot commented Oct 17, 2025

Summary of Changes

Highlights

Footnotes

Uh oh!

googlyrahman commented Oct 17, 2025

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant