From f767f311c50f50812c598587d59a188768ff39a7 Mon Sep 17 00:00:00 2001 From: Haukur Hreinsson Date: Mon, 20 Jul 2026 16:18:02 +0000 Subject: [PATCH] fix: pass cluster_name_prod to deploy-to-prod job The deploy-to-prod job in release-deploy.yml was passing cluster_name_staging as CLUSTER_NAME instead of cluster_name_prod. CLUSTER_NAME is used by the force-new-deployment and wait-for-stable steps in deploy-ecs-service, so enabling FORCE_NEW_DEPLOYMENT on a release deploy would target the wrong cluster. --- .github/workflows/release-deploy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release-deploy.yml b/.github/workflows/release-deploy.yml index 1b68cf5..a69eaaa 100644 --- a/.github/workflows/release-deploy.yml +++ b/.github/workflows/release-deploy.yml @@ -139,5 +139,5 @@ jobs: TERRAFORM_VERSION: ${{ inputs.terraform_version }} TERRAFORM_PATH: '${{ matrix.directory }}/terraform' SERVICE_NAME: ${{ matrix.name }} - CLUSTER_NAME: ${{ inputs.cluster_name_staging }} + CLUSTER_NAME: ${{ inputs.cluster_name_prod }} PRE_APPLIED_RESOURCES: ${{ inputs.pre_applied_resources }}