-
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
[azurerm_web_application_firewall_policy] Fix max_request_body_size_in_kb, file_upload_limit_in_mb for CRS 3.2 #12817
Comments
@tombuildsstuff Shall we just raise the limits and let people figure out version dependency or turn validation into a version-specific function? |
bumped into the same issue - meanwhile on provider |
max_request_body_size_in_kb is fixed while file_upload_limit_in_mb is not. |
`r\azurerm_azurerm_web_application_firewall_policy` fix #12817 by loose `file_upload_limit_in_mb` to 4000.
This functionality has been released in v2.91.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! |
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. |
Community Note
Terraform (and AzureRM Provider) Version
Terraform v0.13.7
Affected Resource(s)
azurerm_web_application_firewall_policy
Expected Behaviour
https://docs.microsoft.com/en-us/azure/web-application-firewall/ag/application-gateway-waf-configuration#waf-request-size-limits
For CRS 3.2 (on the WAF_v2 SKU) and newer, these limits are as follows:
Actual Behaviour
Looks like Terraform still sticks to the old limits.
https://github.com/terraform-providers/terraform-provider-azurerm/blob/v2.70.0/azurerm/internal/services/network/web_application_firewall_policy_resource.go#L268
Error returned when trying to exceed the old limit, regardless of CRS 3.2 has been set.
The text was updated successfully, but these errors were encountered: