From a6d951231ae07d4a543b5b4a99c2e166c4e4ef67 Mon Sep 17 00:00:00 2001 From: gurusai-voleti Date: Mon, 16 Feb 2026 07:39:01 +0000 Subject: [PATCH] chore: Migrate gsutil usage to gcloud storage --- docs/deploy/cloudrun.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/deploy/cloudrun.md b/docs/deploy/cloudrun.md index e70c3d6b..75ae2dfa 100644 --- a/docs/deploy/cloudrun.md +++ b/docs/deploy/cloudrun.md @@ -14,13 +14,13 @@ To set up the `slo-generator` with Terraform, please look at the [terraform-goog Create the GCS bucket that will hold our SLO configurations: ``` -gsutil mb -p ${PROJECT_ID} gs://${BUCKET_NAME} +gcloud storage buckets create gs://${BUCKET_NAME} --project=${PROJECT_ID} ``` Upload the slo-generator configuration to the GCS bucket: ``` -gsutil cp config.yaml gs://${BUCKET_NAME}/ +gcloud storage cp config.yaml gs://${BUCKET_NAME}/ ``` See sample [config.yaml](../../samples/config.yaml) @@ -55,7 +55,7 @@ See sample [slo.yaml](../../samples/cloud_monitoring/slo_gae_app_availability.ya Upload your SLO config to the GCS bucket: ``` -gsutil cp slo.yaml gs://${BUCKET_NAME}/ +gcloud storage cp slo.yaml gs://${BUCKET_NAME}/ ``` Create a Cloud Scheduler job that will hit the service with the SLO config URL: @@ -73,7 +73,7 @@ can deploy an export-only API to Cloud Run: Upload the slo-generator export config to the GCS bucket: ``` -gsutil cp config_export.yaml gs://${BUCKET_NAME}/config_export.yaml +gcloud storage cp config_export.yaml gs://${BUCKET_NAME}/config_export.yaml ``` Deploy the `slo-generator` with `--signature-type=cloudevent` and `--target=run_export`: