-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
frontdoor: updating to use a generated Resource ID Formatter/Parser/Validator #9750
Conversation
This enables this to be threaded through directly from the FrontDoor ID
…match the upcoming generated name
…e for the strict method
…Frontend Endpoint
…rs for HealthProbe
…Web Application Firewall Policy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @tombuildsstuff - LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tombuildsstuff Thanks for the PR, this LGTM as well! 🚀
This has been released in version 2.40.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 = "~> 2.40.0"
}
# ... other configuration ... |
Does it fix #8039 too? |
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 👉 [email protected]. Thanks! |
This PR works around a series of bugs in the FrontDoor API - by parsing these Resource ID's case insensitively and then rewriting them within Terraform, ensuring that these are consistent from Terraform's point of view.
Whilst this works when the
key
of the key-value pair is returned in the incorrect case, unfortunately we can't workaround the value being incorrect - ultimately the FrontDoor Team needs to fix the API to comply with the ARM/HTTP Spec.. but this is the best we can do at this point in time 🤷Fixes #8208