-
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
Trailing period should be omitted from domain name #6389
Comments
After some experimenting with different provider versions, I'm thinking aws made a change in their api, where by a dot is now returned when you call the name attribute of a route 53 dns entry. |
We've been plagued with problems due to this additional period. Does it come from the latest provider from TF when using r53 resources ? |
I'm not aware of any recent changes to the
|
I asked AWS if they had changed anything with the API: "Good day Graham, I have received feedback that no known changes were made to the API, however if you can provide a time when you experienced a discrepancy then the service team can look deeper into the period in question. I will be looking forward to your feedback. Best regards, Kevin D. Check out the AWS Support Knowledge Center, a knowledge base of articles and videos that answer customer questions about AWS services: https://aws.amazon.com/premiumsupport/knowledge-center/?icmpid=support_email_category " |
The dot appears in 1.42 during "refresh", without doing the vpc_id -> vpc { vpc_id } change It appears in aws_route53_zone.name and spreads from there. The dot does not apper when doing "refresh" with 1.41. Although when downgrading from 42->41 Looks like terraform-provider-aws problem. (Using terrafrom 0.11.11) |
Note: this is without apigateway, just plain aws_route53_zone for internal use in VPC. |
#6535 has a similar fix for certificates, but I guess it needs to be applied quite widely. I had to work around it with the reg-ex in that issue. |
This has been released in version 3.0.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 for triage. Thanks! |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Error: Error applying plan:
Terraform and provider versions:
The text was updated successfully, but these errors were encountered: