Skip to content
New issue

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

Importing a gandi_domain seems to require deprecated nameservers field #140

Open
rvandegrift opened this issue Feb 23, 2023 · 1 comment

Comments

@rvandegrift
Copy link

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.

@matthiasr
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants