Skip to content

Commit 59e5dfe

Browse files
chore: migrate gsutil usage to gcloud storage (#13143)
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](http://go/gsutil-gcloud-storage-migration-guide) ([external guide](https://docs.cloud.google.com/storage/docs/gsutil-transition-to-gcloud)). ### 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
1 parent 005557f commit 59e5dfe

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

‎buildscripts/kokoro/android.sh‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,7 @@ fi
156156
# Update the statuses with the deltas
157157

158158
set +x
159-
gsutil cp gs://grpc-testing-secrets/github_credentials/oauth_token.txt ~/
159+
gcloud storage cp gs://grpc-testing-secrets/github_credentials/oauth_token.txt ~/
160160

161161
desc="New DEX reference count: $(printf "%'d" "$new_dex_count") (delta: $(printf "%'d" "$dex_count_delta"))"
162162
echo "Setting status: $desc"

‎buildscripts/kokoro/upload_artifacts.sh‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -51,13 +51,13 @@ find "$LOCAL_MVN_ARTIFACTS" -type f -iname 'protoc-gen-grpc-java-*-osx-aarch_64.
5151

5252

5353
mkdir -p ~/.config/
54-
gsutil cp gs://grpc-testing-secrets/sonatype_credentials/sonatype-upload ~/.config/sonatype-upload
54+
gcloud storage cp gs://grpc-testing-secrets/sonatype_credentials/sonatype-upload ~/.config/sonatype-upload
5555

5656
mkdir -p ~/java_signing/
57-
gsutil cp -r gs://grpc-testing-secrets/java_signing/ ~/
57+
gcloud storage cp -r gs://grpc-testing-secrets/java_signing/ ~/
5858
gpg --batch --import ~/java_signing/grpc-java-team-sonatype.asc
5959

60-
gsutil cat gs://grpc-testing-secrets/dockerhub_credentials/grpcpackages.password \
60+
gcloud storage cat gs://grpc-testing-secrets/dockerhub_credentials/grpcpackages.password \
6161
| docker login --username grpcpackages --password-stdin
6262

6363
# gpg commands changed between v1 and v2 are different.

0 commit comments

Comments
 (0)