Skip to content

chore: migrate gsutil usage to gcloud storage - #2208

Open
gurusai-voleti wants to merge 1 commit into
datacommonsorg:masterfrom
gurusai-voleti:ai-gsutil-migration-0c9519ae882a46069764786fd29ee2c1
Open

chore: migrate gsutil usage to gcloud storage#2208
gurusai-voleti wants to merge 1 commit into
datacommonsorg:masterfrom
gurusai-voleti:ai-gsutil-migration-0c9519ae882a46069764786fd29ee2c1

Conversation

@gurusai-voleti

Copy link
Copy Markdown

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

⚠️ 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.

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 (external guide).

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

Copy link
Copy Markdown
Author

Hi @smarthg-gi, Can we get your review on this PR? Thanks!

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

Copy link
Copy Markdown
Contributor

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 migrates GCS operations in import-automation/executor/run_import.sh from gsutil to gcloud storage. The review feedback highlights two important improvements: appending a trailing slash to the directory path in gcloud storage ls to prevent incorrect prefix matching, and redirecting standard error to /dev/null when reading staging_version.txt to avoid noisy logs if the file is missing.

Comment thread import-automation/executor/run_import.sh
Comment thread import-automation/executor/run_import.sh
@gurusai-voleti gurusai-voleti changed the title Migrate gsutil usage to gcloud storage chore: migrate gsutil usage to gcloud storage Sep 7, 2026
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.

1 participant