Repository navigation
Plan without taking the state lock - #2
Merged
Merged
Conversation
Spaces ignores conditional writes, so a plan that overlaps an apply takes the same lock and fails when releasing it. Plans only read state; only apply takes the lock now.
OpenTofu plan for
|
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
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.
DigitalOcean Spaces ignores conditional writes, so OpenTofu's lock file does not lock. A drift run that overlapped the first CI apply took the same lock and failed releasing it (the plan itself showed no changes).
Plans only read state, so the plan and drift workflows now run
tofu plan -lock=false. Only apply takes the lock, and applies never run in parallel (concurrency group). The README says the same for local runs.