fix: allow cluster deletion (terraform-google-jx#233) #234
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.
Description
Beginning with Terraform's Google provider version 5.0.0+, container clusters deletion protection defaults to
true
which prevents theterraform destroy
command from deleting the cluster. To provide a mechanism for overriding this protection, a new TF variabledelete_protect
is introduced and will be used to set thedeletion_protection
attribute for thegoogle_container_cluster
resource.Which issue this PR fixes
#233
Release notes
You must explicitly set
deletion_protection=false
(and runterraform apply
to write the field to state) in order to destroy a cluster. It is recommended to not set this field (or set it to true) until you're ready to destroy.