Run plan without acquiring the Consul state lock (#136)
ci/woodpecker/push/apply Pipeline was successful
ci/woodpecker/push/apply Pipeline was successful
PR plan pipelines were failing with "Error acquiring the state lock ... OperationTypePlan" when a plan collided with an apply (or another plan) holding the lock on the same Consul-backed state. Plans are read-only and don't need the lock. - `plan`: pass `-lock=false` to `terragrunt ... plan`; `apply` is unchanged and still locks. Reviewed-on: #136 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>
This commit was merged in pull request #136.
This commit is contained in:
@@ -22,7 +22,7 @@ init:
|
|||||||
|
|
||||||
plan: init
|
plan: init
|
||||||
@$(call vault_env) && \
|
@$(call vault_env) && \
|
||||||
terragrunt run --all --parallelism 4 --non-interactive plan
|
terragrunt run --all --parallelism 4 --non-interactive plan -- -lock=false
|
||||||
|
|
||||||
apply: init
|
apply: init
|
||||||
@$(call vault_env) && \
|
@$(call vault_env) && \
|
||||||
|
|||||||
Reference in New Issue
Block a user