From b29294b4ee8a22d2e933c7785c9a9b4e6b491f3d Mon Sep 17 00:00:00 2001 From: Deirdre Connolly Date: Sat, 6 Mar 2021 01:46:05 -0500 Subject: [PATCH] Explicitly auto-delete additional cache disks This property is supposedly set to 'true' by default, but we are still leaving disks behind. Perhaps because: "...if the disk is later detached from the instance, this option won't apply." https://cloud.google.com/sdk/gcloud/reference/compute/instance-templates/create-with-container#--disk Resolves #1845 --- .github/workflows/cd.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/cd.yml b/.github/workflows/cd.yml index e53e7093f..5a18446f5 100644 --- a/.github/workflows/cd.yml +++ b/.github/workflows/cd.yml @@ -85,7 +85,7 @@ jobs: run: | gcloud compute instance-templates create-with-container "zebrad-$BRANCH_NAME-$SHORT_SHA" \ --container-image "gcr.io/$PROJECT_ID/$REPOSITORY/$BRANCH_NAME:$SHORT_SHA" \ - --create-disk name=zebrad-cache-$SHORT_SHA,size=100GB,type=pd-balanced \ + --create-disk name=zebrad-cache-$SHORT_SHA,auto-delete=yes,size=100GB,type=pd-balanced \ --container-mount-disk mount-path="/zebrad-cache",name=zebrad-cache-$SHORT_SHA \ --machine-type n2d-standard-4 \ --service-account cos-vm@zealous-zebra.iam.gserviceaccount.com \