When preparing for changes with Terraform, we are always playing the revert operation to restore the previous state. While playing the restore with the DNS configuration and your provider, we realized it's impossible to reactivate the LiveDNS through Terraform resource.
Example
With this content as the current state of domain:
# Current state
resource "gandi_livedns_domain" "example_com" {
name = "example.com"
}
you plan a migration to another DNS provider by replacing the previous content and you do apply it for one of them to validate:
# Next state
resource "gandi_nameservers" "example_com" {
domain = "example.com"
nameservers = ["ABC", "DEF", "GHI"]
}
The change is correctly applied. But if you to revert back to the current state, cancelling the change for the test domain, the DNS information are not updated on your services (verified on the web UI). The DNS servers are still listed with the next state values :disappointed: - making any revert operation fully manual. Or say differently it's impossible to activate the LiveDNS from Terraform resources if it was set to external.
Context
When preparing for changes with Terraform, we are always playing the revert operation to restore the previous state. While playing the restore with the DNS configuration and your provider, we realized it's impossible to reactivate the LiveDNS through Terraform resource.
Example
With this content as the current state of domain:
you plan a migration to another DNS provider by replacing the previous content and you do
applyit for one of them to validate:The change is correctly applied. But if you to revert back to the current state, cancelling the change for the test domain, the DNS information are not updated on your services (verified on the web UI). The DNS servers are still listed with the next state values :disappointed: - making any revert operation fully manual. Or say differently it's impossible to activate the LiveDNS from Terraform resources if it was set to external.