-
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: refactoring & ensuring ID's are consistent #8146
Conversation
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.
Hi @tombuildsstuff - A few minor comments, but otherwise LGTM 👍
azurerm/internal/services/frontdoor/frontdoor_firewall_policy_resource.go
Outdated
Show resolved
Hide resolved
Also fixing issues where fields aren't set into the state to ensure that fields always have a value
…king the wrong resource name
…precating `resource_group_name`
…ect case at import time
07b3253
to
75223f4
Compare
This has been released in version 2.24.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.24.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! |
This PR introduces quite a large refactoring to the Frontdoor resources - namely this ensures that all fields are always set - and ensures that ID's are consistent, so that users can rely on these.
Supersedes #8046
Fixes #8036