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
The active property in azurerm_cdn_frontdoor_security_policy.security_policies.firewall.association.domain is not configurable, contrary to what the documentation states
#28364
Open
1 task done
kaganmersin opened this issue
Dec 22, 2024
· 1 comment
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 comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.
Error: Value for unconfigurable attribute
with azurerm_cdn_frontdoor_security_policy.default["default"],
on waf.tf line 162, in resource "azurerm_cdn_frontdoor_security_policy""default":
162: association {
Can't configure a value for"security_policies.0.firewall.0.association.0.domain.0.active": its valuewill be decided automatically based on the result of applying this
Expected Behaviour
No response
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
It seems this argument is unconfigurable unlike it seems configurable in documentation and I believe this argument should be omitted in the documentation
Is there an existing issue for this?
Community Note
Terraform Version
1.9.4
AzureRM Provider Version
4.14.0
Affected Resource(s)/Data Source(s)
azurerm_cdn_frontdoor_security_policy
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
No response
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: