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
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 "+1" or "me too" comments, 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
Description
Shouldn't the application gateway sku capacity limit be increased to azure's limit of 32. In the Azure portal I can create a WAF_Large WAF with resource count of 32.
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
Sep 29, 2019
Community Note
Description
Shouldn't the application gateway sku capacity limit be increased to azure's limit of 32. In the Azure portal I can create a WAF_Large WAF with resource count of 32.
Terraform (and AzureRM Provider) Version
Terraform v0.12.6
provider.azurerm v1.32.1
Affected Resource(s)
azurerm_application_gateway
Terraform Configuration Files
Debug Output
Terraform command 'plan' failed with exit code '1'.: expected sku.0.capacity to be in the range (1 - 10), got 32
Expected Behavior
Deploy Azure's limit of 32
Actual Behavior
Error message stating your limited to a range capacity of 10
Steps to Reproduce
terraform plan
The text was updated successfully, but these errors were encountered: