chore: Migrate gsutil usage to gcloud storage#2707
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request automates the migration from gsutil to gcloud storage across various files, including shell scripts and documentation. The automated replacements of commands like gsutil cp to gcloud storage cp and gsutil mb to gcloud storage buckets create are correct. I have left one comment on an outdated comment in a shell script that should be updated for maintainability. Otherwise, the changes look good. As noted in the pull request description, please ensure these changes are thoroughly tested.
|
Is this ready for review? It looks like there is an open comment that needs resolution and it looks like in the last commit, several items were reverted and I am not sure that that is what we want. Please advise. Thanks. |
yes the PR is ready for review, the changes reverted are already in PR's #2706 and #2705 |
vchudnov-g
left a comment
vchudnov-g
left a comment
There was a problem hiding this comment.
These files are auto-generated from Discovery files, which in turn come from internal API definitions. Any changes made directly here will be overwritten next time an internal change propagates.
Please contact the appropriate API teams internally to update their files. When those changes are released and propagate to the Discovery server, this repo will eventually pick them up.
3 participants
Automated: Migrate {target_path} from gsutil to gcloud storage
This CL is part of the on going effort to migrate from the legacy
gsutiltool to the new and improvedgcloud storagecommand-line interface.gcloud storageis the recommended and modern tool for interacting with Google Cloud Storage, offering better performance, unified authentication, and a more consistent command structure with othergcloudcomponents. 🚀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.
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
gsutilandgcloud storagethat 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 rsynccommand has a different file deletion logic thangsutil 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 CLIteam 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.comWe appreciate your partnership in this important migration effort!
#gsutil-migration