Note added for forced casing at runtime. #3695
Conversation
While working with the Azure MySQL PaaS it was identified that the `name` of the resource was forced to lower case in Azure at apply time; If uppercase letters were used in the Terraform Plan it was immediately out-of-date once applied and flagged the freshly created resource Destroy/Create at next `planning`.
There was a problem hiding this comment.
Hi @jblose,
Thanks for bringing this to our attention. I think a better change then updating the docs might be to change the resource to prevent uppercase characters for the server name? That way users who don't see the docs won't get tripped up. What do you think?
|
@katbyte Thank you for following up on the PR. That works for me, correcting the provider over the documentation is the right way to go long term. I may try and report it on the Azure project as well since "normally" when attempting to name something incorrectly Azure returns an |
No worries at all and thank you, I was hoping to get around to it this past weekend and ended up sidetracked on another project. Keep fighting the good fight! |
|
This has been released in version 1.31.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.31.0"
}
# ... other configuration ... |
|
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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
ghost
locked and limited conversation to collaborators
While working with the Azure MySQL PaaS it was identified that the
nameof the resource was forced to lower case in Azure at apply time; If uppercase letters were used in the Terraform Plan it was immediately out-of-date once applied and flagged the freshly created resource Destroy/Create at nextplanning.