azurerm_private_dns_a_record_resource - currently validate the name property by allowing @s

[stephybun]

Fixes #12406

[tombuildsstuff]

one thought about refactoring this but this otherwise LGTM 👍

[katbyte]

Thanks @stephybun - LGTM now 🏗️

[github-actions]

This functionality has been released in v2.73.0 of the Terraform 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!

[calloes]

Why is this changed ? apex dns records are valid in private dns zones. Our existing code now fails.

Internal DNS zone can have a valid root record represented by @

�[31m
�[1m�[31mError: �[0m�[0m�[1m"name" cannot contain @�[0m

�[0m on .terraform/modules/private_dns/main.tf line 7, in resource "azurerm_private_dns_a_record" "zone_root_a_record":
7: name = �[4m"@"�[0m
�[0m
�[0m�[0m

[stephybun]

Hello @calloes, yep you are right. We've reverted the validation on name that's causing your code to fail and added validation on the number of allowed records in this PR #13093 which will be released in v2.74.0 on Thursday.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.