-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
IPv6 data attribute documented but not working #12785
Comments
@realflash ctrl+f for 'ipv6' on https://github.com/terraform-providers/terraform-provider-aws/blob/master/aws/data_source_aws_instance.go now returns 0 results. Based on what you said in #14473, it seems to me it was removed. |
Still broken in provider.aws v3.20.0 |
For those still affected by this, @rick-masters has asked you to react to his pull request #17859 in order to help maintainers gauge prioritisation for this to be merged. If you want this fixed, go vote now. |
This functionality has been released in v3.57.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Terraform Version
Terraform v0.12.24
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
No error output.
Actual Behavior
Steps to Reproduce
terraform plan
Important Factoids
It was me that "discovered" that an ipv6_addresses attribute existed but wasn't documented in hashicorp/terraform#14473 . If memory serves I was using the attribute in a route 53 record in the same root module as the instance, not as a data source. Now I come to use it conjunction with spot instances to gather data on the instance that has been deployed, I find it doesn't work. I wonder if it was missing from the aws_instance resource documentation at the time (it's there now and works), but in my commit I added it to the aws_instance data source documentation, thus documenting something Ihat was different to what I had actually tested. Or possibly that attribute was there and has subsequently been removed, which would make this a regression.
References
The text was updated successfully, but these errors were encountered: