From fe117dc1d93faca60525f0a1bf3c0ce53ac3ca6c Mon Sep 17 00:00:00 2001 From: Jeremi Piotrowski Date: Wed, 27 Sep 2023 16:04:15 +0200 Subject: [PATCH] ci-automation: Switch to managed identity on azure Switch to using a managed identity instead of file based credentials for running kola/ore (not plume). This covers our test subscription, but not our publishing subscription. Signed-off-by: Jeremi Piotrowski --- ci-automation/garbage_collect_cloud.sh | 13 +------------ ci-automation/vendor-testing/azure.sh | 8 +------- 2 files changed, 2 insertions(+), 19 deletions(-) diff --git a/ci-automation/garbage_collect_cloud.sh b/ci-automation/garbage_collect_cloud.sh index 034edd83b0..043e10efe7 100755 --- a/ci-automation/garbage_collect_cloud.sh +++ b/ci-automation/garbage_collect_cloud.sh @@ -3,18 +3,7 @@ set -euo pipefail timeout --signal=SIGQUIT 60m ore aws gc --access-id "${AWS_ACCESS_KEY_ID}" --secret-key "${AWS_SECRET_ACCESS_KEY}" timeout --signal=SIGQUIT 60m ore do gc --config-file=<(echo "${DIGITALOCEAN_TOKEN_JSON}" | base64 --decode) timeout --signal=SIGQUIT 60m ore gcloud gc --json-key <(echo "${GCP_JSON_KEY}" | base64 --decode) -# Because the Azure file gets read multiple times it can't be passed like <(cmd) because bash backs this FD -# by a pipe meaning the data is gone after reading. We can create an FD (the FD number is assigned to -# variable through exec {NAME}) manually and use a file under /tmp to back it instead, allowing multiple -# reads. -echo "${AZURE_PROFILE}" | base64 --decode > /tmp/azure_profile -exec {azure_profile} /tmp/azure_auth -exec {azure_auth}