-
Notifications
You must be signed in to change notification settings - Fork 63
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
ns1_zone does not support "primaries" or "secondaries" using IPv6 addresses #106
Comments
Hi there 👋 Thanks for reporting this issue, definitely appreciated! I believe the issue you're seeing is actually a limitation of NS1, rather than a fault of the Terraform provider (the error you're seeing is being returned by the API, not generated from the Terraform provider). As noted in NS1's API documentation, only IPv4 addresses are currently supported for primary and secondary nameservers ( That said, I do think it would be valuable to get a validator on these fields to make this limitation more transparent to users of this provider. I've create #107 to track this enhancement. |
I opened NS1 Support Ticket 23797 for a feature request to support IPv6 in the API. I will comment when I have a reference to the actual feature request. |
Also, the Terraform provider documentation for |
Excellent point! I've created #108 to update the documentation for those parameters and clarify this limitation. Thanks for contacting support with that feature request, I'm sure that will help them prioritize this enhancement. To ensure Issues for this repo remain focused on the Terraform provider, I'm going to recommend we don't track feature requests against the NS1 platform here. Once NS1 supports IPv6 we can create new stories and open additional issues in this repo to enable support via Terraform. I recommend we close out this issue once the documentation is updated. |
The intent of the feature request info being here is not to track the feature as part of the TF provider, but to communicate with the TF Provider developers (aka "you") that a request was submitted and that you can track that stuff internally for later story development. Not fully-supporting IPv6 is a major shortcoming of NS1. |
@chris-zenfolio - Understood, thanks for the clarification and apologies for the misunderstanding on my part! |
#108 has been merged, should take affect on next minor or patch version release. |
Terraform Version
Affected Resource(s)
ns1_zone
Terraform Configuration Files
Debug Output
I think the error message is pretty clear on this one, since it gives the error and why it failed (regex failure).
Panic Output
No crash output
Expected Behavior
The
terraform apply
would have succeeded and the secondary zones created with a primary NS that has an IPv6 address.Actual Behavior
terraform init
andterraform plan
succeeded with no issues, butterraform apply
failed with the following error (repeated for every secondary zone I defined):Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
References
None that I know of.
The text was updated successfully, but these errors were encountered: