You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I imported a domain whose nameservers are pointed to cloudflare. It worked, but the provider imported the nameservers field on the gandi_domain resource. The config now triggers the deprecation warning. It'd be better to not import nameservers and require a second import for the associated gandi_nameservers.
But now I'm not really clear on how to fix it. I tried removing nameservers from my config and modifying the state data to make nameservers null. But terraform still thinks it should remove the existing nameservers - not sure why.
I also imported a domain with LiveDNS enabled, and it doesn't have this problem.
The text was updated successfully, but these errors were encountered:
I had related issues with the nameservers field getting populated after I set nameservers with gandi_nameservers. Subsequently, Terraform wanted to unset it.
I worked around this with
lifecycle {
ignore_changes=[
# "Error: domain owner contact update is currently not supported"owner,
# The nameservers attribute is deprecated, but when creating nameservers# the new way, it is still populated on refresh, leading to a cycle of# diffs.nameservers,
]
}
This causes Terraform to complain about use of a deprecated attribute, but at least it doesn't break my domain.
I imported a domain whose nameservers are pointed to cloudflare. It worked, but the provider imported the
nameservers
field on thegandi_domain
resource. The config now triggers the deprecation warning. It'd be better to not importnameservers
and require a second import for the associatedgandi_nameservers
.But now I'm not really clear on how to fix it. I tried removing
nameservers
from my config and modifying the state data to makenameservers
null. But terraform still thinks it should remove the existing nameservers - not sure why.I also imported a domain with LiveDNS enabled, and it doesn't have this problem.
The text was updated successfully, but these errors were encountered: