-
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
[Bug]: Breaking change in route53 record for alias setting #29072
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Changed in #28894. |
Hi @lovrek93, thank you for submitting this. The provider was previously failing silently when more than one It looks like you're trying to conditionally create the I've tried debugging this, but I'm not able to simply place the |
Since we haven't heard back in several months, I'm going to close this issue. If you are still encountering the problem, please open a new issue. |
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. |
Terraform Core Version
1.0.9
AWS Provider Version
4.51.0
Affected Resource(s)
aws_route53_record
Expected Behavior
Alias configuration in TF should create Alias configuration.
Actual Behavior
Getting following error:
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Adding a new record with alias configuration and using newest AWS provider gives the error.
Debug Output
No response
Panic Output
No response
Important Factoids
This happens only on version 4.51.0 (works on all prior versions).
I found this issue that mentions the breaking change in file internal/service/route53/record.go on line 91
It seems to me that this breaking change was already implemented in version 4.51.0 and hence this problem is happening.
My advice would be revert "alias" for record to previous configuration (like on 4.50.0 for example).
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: