We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have a DNS zone (example.com), in which I deploy multiple instances of the same Terraform script (with different names, of course).
To prevent the DNS zone from being deleted when terraform destroy has been issued, I have protected my DNS zone from being destroyed.
terraform destroy
resource "hetznerdns_zone" "example_com_dns_zone" { name = "example.com" ttl = 86400 lifecycle { prevent_destroy = true } }
Unfortunately, on a destroy, no DNS records will be destroyed, even though I marked the DNS records as "do not prevent destroy".
resource "hetznerdns_record" "server_example_com_dns_record_a" { zone_id = hetznerdns_zone.example_com_dns_zone.id name = "server" type = "A" value = "127.0.0.1" ttl = 60 lifecycle { prevent_destroy = false } }
Please delete DNS records, when they are not protected, but the DNS zone is.
The current version (2.1.0) will not delete the DNS records, despite being not protected.
The text was updated successfully, but these errors were encountered:
Oh, prevent_destroy lifecycle option is not supported currently. I see the value of this and I'm happy for contributions.
prevent_destroy
Sorry, something went wrong.
No branches or pull requests
I have a DNS zone (example.com), in which I deploy multiple instances of the same Terraform script (with different names, of course).
To prevent the DNS zone from being deleted when
terraform destroy
has been issued, I have protected my DNS zone from being destroyed.Unfortunately, on a destroy, no DNS records will be destroyed, even though I marked the DNS records as "do not prevent destroy".
Please delete DNS records, when they are not protected, but the DNS zone is.
The current version (2.1.0) will not delete the DNS records, despite being not protected.
The text was updated successfully, but these errors were encountered: