From 2f721f229c1ca6ccc35d4e3aed65801dc7a61bcc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gon=C3=A7alo=20Heleno?= Date: Tue, 6 Sep 2022 13:28:41 +0200 Subject: [PATCH] fix: use terraform-bin to solve output issues See [this issue](https://github.com/hashicorp/setup-terraform/issues/167) for an explanation. --- .github/workflows/terraform_schedule_plan_destroy.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/terraform_schedule_plan_destroy.yaml b/.github/workflows/terraform_schedule_plan_destroy.yaml index 55717a8..d2dfb03 100644 --- a/.github/workflows/terraform_schedule_plan_destroy.yaml +++ b/.github/workflows/terraform_schedule_plan_destroy.yaml @@ -29,7 +29,7 @@ jobs: AWS_DEFAULT_REGION: ${{ secrets.AWS_DEFAULT_REGION }} - name: Delete some resources on the state file - run: terraform state rm $(terraform state list | grep 'argocd_application\|argocd_project\|kubernetes_\|helm_') + run: terraform state rm $(terraform-bin state list | grep 'argocd_application\|argocd_project\|kubernetes_\|helm_') continue-on-error: true # This is to avoid failed workflows and the consequent noise when the scheduled destroy runs on the days we have not created the test deployment env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}