Skip to content

chore: Migrate gsutil usage to gcloud storage#6792

Merged
tarasmadan merged 2 commits intogoogle:masterfrom
gurusai-voleti:ai-gsutil-migration-51ceae9c9fc248e19e722cbde95dcfb0
Mar 20, 2026
Merged

chore: Migrate gsutil usage to gcloud storage#6792
tarasmadan merged 2 commits intogoogle:masterfrom
gurusai-voleti:ai-gsutil-migration-51ceae9c9fc248e19e722cbde95dcfb0

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

@a-nogikh
Copy link
Collaborator

Please drop the merge commits - they will not pass our CI checks. On this project, we rebase instead of merging.

@gurusai-voleti gurusai-voleti force-pushed the ai-gsutil-migration-51ceae9c9fc248e19e722cbde95dcfb0 branch from 143ae10 to 86d2a07 Compare March 19, 2026 14:25
@gurusai-voleti
Copy link
Contributor Author

Please drop the merge commits - they will not pass our CI checks. On this project, we rebase instead of merging.

updated

a-nogikh
a-nogikh previously approved these changes Mar 19, 2026
@gurusai-voleti gurusai-voleti force-pushed the ai-gsutil-migration-51ceae9c9fc248e19e722cbde95dcfb0 branch from 86d2a07 to 2b024c3 Compare March 19, 2026 14:46
@gurusai-voleti
Copy link
Contributor Author

can you help merge as well @a-nogikh

@a-nogikh
Copy link
Collaborator

There are a few failing checks that currently prevent merging:

./tools/check-commits.sh
Error: Wrong commit subject format: 'Update Dockerfile'. Please use 'main/affected/package: short change description'. See docs/contributing.md for details. Regex pattern used to check commit subjects is '^(Revert "|(([a-z0-9/_.-]+|Makefile|AUTHORS|CONTRIBUTORS|README.md)(, )?)+:\ [^A-Z].+[^.]$)'.
./tools/check-copyright.sh
./tools/check-language.sh
./tools/check-whitespace.sh
Error: Wrong commit subject format: 'chore: Migrate gsutil usage to gcloud storage'. Please use 'main/affected/package: short change description'. See docs/contributing.md for details. Regex pattern used to check commit subjects is '^(Revert "|(([a-z0-9/_.-]+|Makefile|AUTHORS|CONTRIBUTORS|README.md)(, )?)+:\ [^A-Z].+[^.]$)'.
2 commits checked for format style (git log -n 2 2b024c3b81858312d41f527bec6ca05dc1f7bb1a)
289 files checked for whitespaces
1487 files checked for copyright statement

@gurusai-voleti gurusai-voleti force-pushed the ai-gsutil-migration-51ceae9c9fc248e19e722cbde95dcfb0 branch 2 times, most recently from 86d2a07 to 6ef4398 Compare March 20, 2026 08:07
@gurusai-voleti gurusai-voleti force-pushed the ai-gsutil-migration-51ceae9c9fc248e19e722cbde95dcfb0 branch from 6ef4398 to cadb316 Compare March 20, 2026 08:07
@gurusai-voleti
Copy link
Contributor Author

There are a few failing checks that currently prevent merging:

./tools/check-commits.sh
Error: Wrong commit subject format: 'Update Dockerfile'. Please use 'main/affected/package: short change description'. See docs/contributing.md for details. Regex pattern used to check commit subjects is '^(Revert "|(([a-z0-9/_.-]+|Makefile|AUTHORS|CONTRIBUTORS|README.md)(, )?)+:\ [^A-Z].+[^.]$)'.
./tools/check-copyright.sh
./tools/check-language.sh
./tools/check-whitespace.sh
Error: Wrong commit subject format: 'chore: Migrate gsutil usage to gcloud storage'. Please use 'main/affected/package: short change description'. See docs/contributing.md for details. Regex pattern used to check commit subjects is '^(Revert "|(([a-z0-9/_.-]+|Makefile|AUTHORS|CONTRIBUTORS|README.md)(, )?)+:\ [^A-Z].+[^.]$)'.
2 commits checked for format style (git log -n 2 2b024c3b81858312d41f527bec6ca05dc1f7bb1a)
289 files checked for whitespaces
1487 files checked for copyright statement

changed the commit messages

@tarasmadan tarasmadan enabled auto-merge March 20, 2026 09:18
@tarasmadan tarasmadan added this pull request to the merge queue Mar 20, 2026
Merged via the queue into google:master with commit 2dee23a Mar 20, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants