Conversation
init operations only actually need state locking when migrating state between backends. still possible to enable state locking when needed.
for workflow runs where infra will potentially be changed, ie. goals include any of: [all, apply, apply-on-pr, destroy, destroy-on-pr], concurrency is as before: one wf run per environment active at a time. for workflow runs where infra will _not_ be changed: allow running all wf runs in paralell. to achieve this terraform's backend state locking is disabled in these cases.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
changes
Introduce options to disable state locking during
terraform initandterraform planoperations. Update CI workflow to allow parallel execution of workflows when infrastructure changes are not involved, while maintaining state locking for critical operations.details
terraform init.terraform plan.new concurrency strategy
for workflow runs where infra will potentially be changed, ie. goals include any of: [all, apply, apply-on-pr, destroy, destroy-on-pr], concurrency is as before: one wf run per environment active at a time.
for workflow runs where infra will not be changed: allow running all wf runs in paralell. to achieve this terraform's backend state locking is disabled in these cases.
commits