chore: Migrate gsutil usage to gcloud storage - #14931
Conversation
|
gurusai-voleti is a new contributor to projects/wolfssl. The PR must be approved by known contributors before it can be merged. The past contributors are: hunsche, JacobBarthelmeh, maflcko, guidovranken, ejohnstown, philljj, Uriah-wolfSSL, tim-weller-wolfssl |
|
|
||
| def _gsutil_execute(*args, parallel=True): | ||
| """Executes a gsutil command, passing |*args| to gsutil and returns the | ||
| """Executes a gcloud storage command, passing |*args| to it and returns the |
There was a problem hiding this comment.
Reviewer: I would be careful about approving this since you would need to test it on a live cifuzz run (I can share how I do this) to verify it doesn't break. I think it might break because I think I only installed gsutil in the docker containers because gcloud took up 1 GB of space.
There was a problem hiding this comment.
@sushantkhanna FYI, reviewer asking to test the setup, can you help with you opinion in this case
492dce0 to
e2dec1e
Compare
e2dec1e to
cd15d3c
Compare
cd15d3c to
e221070
Compare
ViniciustCosta
left a comment
ViniciustCosta
left a comment
There was a problem hiding this comment.
Hey @gurusai-voleti could you split this PR into smaller ones?
- One for the changes under
/docs, which should be trivial to land - Multiple for the changes under
/infrathat should target specific parts of the infra folder (base-images, builds, cifuzz, etc.) - One for the changes under
/projectswhich are specific for the onboarded projects build files
Thanks!
created multiple PRs |
|
Closing as we are landing these changes in smaller PRs |
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