From 7f64d95a35b0859964454b5743ac6f4b405c2434 Mon Sep 17 00:00:00 2001 From: Stefan Sauer Date: Tue, 1 Oct 2024 10:30:35 +0200 Subject: [PATCH] Switch to artifact registry. (#450) This was reenabling the contaienrregistry api in tests. --- deploy.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy.sh b/deploy.sh index 5de9ee08..e103f331 100755 --- a/deploy.sh +++ b/deploy.sh @@ -91,11 +91,11 @@ function prepare_source_install { //src/go/cmd/setup-robot:setup-robot.push \ //src/go/cmd/synk - # TODO(rodrigoq): the containerregistry API would be enabled by Terraform, but + # TODO(rodrigoq): the artifactregistry API would be enabled by Terraform, but # that doesn't run until later, as it needs the digest of the setup-robot # image. Consider splitting prepare_source_install into source_install_build # and source_install_push and using Terraform to enable the API in between. - gcloud services enable containerregistry.googleapis.com \ + gcloud services enable artifactregistry.googleapis.com \ --project "${GCP_PROJECT_ID}" # `setup-robot.push` is the first container push to avoid a GCR bug with parallel pushes on newly