Add a poka-yoke to prevent unintentional destroy #350
Closed
Conversation
This file contains 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
It's quite easy to make a config change that requires the cluster to be destroyed and recreated. This is usually not what you want since the state of the cluster will be lost. This config will prevent terraform from trying to apply a change that requires the cluster to be destroyed ... if that is really what you wanted to do you must set `prevent_destroy = false` first
|
Currently there is no way to do this without hardcoding This would also make the module untestable (at least with our current cleanup strategy). |
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.
It's quite easy to make a config change that requires the cluster to be destroyed and recreated. This is usually not what you want since the state of the cluster will be lost.
This config will prevent terraform from trying to apply a change that requires the cluster to be destroyed ... if that is really what you wanted to do you must set
prevent_destroy = falsefirst