chore: Migrate gsutil usage to gcloud storage#1084
chore: Migrate gsutil usage to gcloud storage#1084gurusai-voleti wants to merge 2 commits intogoogle:mainfrom
Conversation
gurusai-voleti
requested review from
shevek-google and
vladislav-sidorovich
as code owners
| log_exec "Creating bucket: ${BQMS_GCS_BUCKET}." \ | ||
| "Could not create bucket: ${BQMS_GCS_BUCKET}." \ | ||
| gsutil mb -l "${BQMS_GCS_BUCKET_LOCATION}" "gs://${BQMS_GCS_BUCKET}" | ||
| gcloud storage buckets create "gs://${BQMS_GCS_BUCKET}" --location="${BQMS_GCS_BUCKET_LOCATION}" |
There was a problem hiding this comment.
Curious that the agent put the --location last here, whereas in the later examples, it put it before the non-option argument. POSIX says the latter is correct, I think accepting this variant was originally a GNU extension.
There was a problem hiding this comment.
no issue both the way it works, before submitting the PR for review our team ensure all the commands works
There was a problem hiding this comment.
@shevek-google any update on the review and merge of this PR
|
This PR is stale because it has been open 35 days with no activity. Remove "stale" label or comment or this will be closed in 14 days. |
|
@shevek-google any update review and merge? |
before merging please verify all checks are green so it wont be any issue, if needed we can help fix issues if any |
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