Migrate gsutil usage to gcloud storage#2605
Migrate gsutil usage to gcloud storage#2605bhandarivijay-png wants to merge 4 commits intoGoogleCloudPlatform:masterfrom
Conversation
|
Hi @bhandarivijay-png. Thanks for your PR. I'm waiting for a GoogleCloudPlatform member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Update export_disk_ext.sh
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bhandarivijay-png The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| - name: 'gcr.io/cloud-builders/gsutil' | ||
| args: ['cp', '/workspace/linux/*', 'gs://$PROJECT_ID/$_RELEASE/linux/'] | ||
| - name: 'gcr.io/cloud-builders/gcloud' | ||
| entrypoint: 'gcloud' |
There was a problem hiding this comment.
do we need entrypoint set in rollout/cli_tools_cloudbuild_build.yaml as well?
| - name: 'gcr.io/cloud-builders/gsutil' | ||
| args: ['cp', '/workspace/linux/*', 'gs://$PROJECT_ID/$_RELEASE/linux/'] | ||
| - name: 'gcr.io/cloud-builders/gcloud' | ||
| entrypoint: 'gcloud' |
There was a problem hiding this comment.
-
With the
gcr.io/cloud-builders/gcloudimage being proposed, we shouldn't need to specifyentrypointat all. Thegcloudbinary is the default entrypoint for these gcloud images already. -
However, is there a reason not to use cloud-sdk image instead:
gcr.io/google.com/cloudsdktool/cloud-sdk? The gcloud image prints a notice suggesting to usecloud-sdk, before actually runninggcloud. -
If we switch to the cloud-sdk image, then we will need the
entrypoint: 'gcloud'. If we don't switch, let's remove the redundant entrypoint.
4 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