Anas Kadam
03/20/2023, 7:26 PMatlantis
plans without locking
2. On PR approval and passing merge checks, atlantis
plans with locking and applies
I tried looking into custom workflows, and my idea was to use two custom workflows:
1. Workflow 1: plans without locking without any requirements
2. Workflow 2: plans and applies with approved and mergeable requirements
But I am unsure how to null or not execute apply on workflow 1.
The issue we have is we want atlantis
locking but run into frequent issues where someone else grabs a lock and the PR is not in a mergeable or approved state. It wastes time to ask the PR owner to unlock and leads into lock contention.PePe Amengual
03/20/2023, 7:41 PMAnas Kadam
03/20/2023, 7:48 PM-lock=false
that we can use, no?PePe Amengual
03/20/2023, 7:52 PMAnas Kadam
03/20/2023, 7:53 PMPePe Amengual
03/20/2023, 7:53 PM- plan:
extra_args: ["-lock", "false"]
repo_locking: false
is what you wantAnas Kadam
03/20/2023, 7:57 PMPePe Amengual
03/20/2023, 7:58 PMAnas Kadam
03/20/2023, 7:59 PMPePe Amengual
03/20/2023, 7:59 PMworkflows:
myworkflow:
plan:
steps:
- run: my-custom-command arg1 arg2
- init
- plan:
extra_args: ["-lock", "false"]
- run: my-custom-command arg1 arg2
apply:
steps:
- run: echo hi
- apply
repo_locking: false
will workAnas Kadam
03/20/2023, 8:01 PMPePe Amengual
03/20/2023, 8:01 PMAnas Kadam
03/20/2023, 8:02 PMPePe Amengual
03/20/2023, 8:03 PMatlantis plan -lock=false
manuallyAnas Kadam
03/20/2023, 8:03 PMPePe Amengual
03/20/2023, 8:03 PM