Add automatic terraform lock handling to deploy and destroy scripts #409
Conversation
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
- Add proactive lock detection and clearing after terraform init - Add reactive lock recovery on apply/destroy failures - Apply to both common and cluster terraform stacks - Prevents failures from stale locks left by incomplete operations
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.
Issue #, if available:
Description of changes:
When cloudformation tried to recreate the stack, sometimes, it is not working due to terraform lock.
the goal of this change is to allow the script to force unloack before trying again
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.