You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
aws_route53_record
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Error: InvalidInput: 1 validation error detected: Value 'domainkey' at 'startRecordType' failed to satisfy constraint: Member must satisfy enum value set: [AAAA, A, CAA, NS, SOA, SPF, MX, PTR, CNAME, DS, TXT, SRV, NAPTR]
status code: 400, request id: cf2fa2bc-ab93-4172-87fd-d4f942b24138
Panic Output
Expected Behavior
That it works to import DNS records that has underscores anywhere in the name.
Actual Behavior
Right now it only works to have an underscore in the beginning of the name, fixed by this. The initial problem reported by this is however not fixed.
Steps to Reproduce
Try to import a name of this format: ABCDEF_foo1._domainkey_CNAME
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Expected Behavior
That it works to import DNS records that has underscores anywhere in the name.
Actual Behavior
Right now it only works to have an underscore in the beginning of the name, fixed by this. The initial problem reported by this is however not fixed.
Steps to Reproduce
Try to import a name of this format:
ABCDEF_foo1._domainkey_CNAME
Important Factoids
References
The text was updated successfully, but these errors were encountered: