Skip to content
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_application_gateway resource update to reflect priority is mandatory when using network api 2021-08-01 #17079

Open
1 task done
bubbletroubles opened this issue Jun 2, 2022 · 3 comments

Comments

@bubbletroubles
Copy link
Contributor

bubbletroubles commented Jun 2, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • 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

The issue #16793 updated the documentation to reflect priority is now mandatory on the azurerm_application_gateway resource.

This issue is to track updating the resource schema to reflect that priority is now mandatory, and include priority in the example.

New or Affected Resource(s)/Data Source(s)

azurerm_application_gateway

Potential Terraform Configuration

See pull request #16849

References

#16849
#16793

@jindrichskupa
Copy link

jindrichskupa commented Jun 13, 2022

I really hate MS/Azure SKU policy but this parametr can't be mandatory.

│ Error: Missing required argument
│ 
│   on application_gw.tf line 116, in resource "azurerm_application_gateway" "public":
│  116:   request_routing_rule {
│ 
│ The argument "priority" is required, but no definition was found.

but

│ Error: updating Application Gateway: (Name "agw-xxxx-westeurope-001" / Resource Group "rg-xxxx-westeurope"): network.ApplicationGatewaysClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="ApplicationGatewayFeatureCannotBeEnabledForSelectedSku" Message="Application Gateway /subscriptions/xxx/resourceGroups/rg-xxxx-westeurope/providers/Microsoft.Network/applicationGateways/agw-xxxx-westeurope-001/requestRoutingRules/vnet-gateway-westeurope-rqrt does not support Priority for the selected SKU tier WAF. Supported SKU tiers are Standard_v2,WAF_v2." Details=[]

@EppO
Copy link
Contributor

EppO commented Jun 16, 2022

I hit the same issue. I suspect it occurs when using Application Gateway v1

@V3dmack
Copy link

V3dmack commented Jul 4, 2022

I really hate MS/Azure SKU policy but this parametr can't be mandatory.

│ Error: Missing required argument
│ 
│   on application_gw.tf line 116, in resource "azurerm_application_gateway" "public":
│  116:   request_routing_rule {
│ 
│ The argument "priority" is required, but no definition was found.

but

│ Error: updating Application Gateway: (Name "agw-xxxx-westeurope-001" / Resource Group "rg-xxxx-westeurope"): network.ApplicationGatewaysClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="ApplicationGatewayFeatureCannotBeEnabledForSelectedSku" Message="Application Gateway /subscriptions/xxx/resourceGroups/rg-xxxx-westeurope/providers/Microsoft.Network/applicationGateways/agw-xxxx-westeurope-001/requestRoutingRules/vnet-gateway-westeurope-rqrt does not support Priority for the selected SKU tier WAF. Supported SKU tiers are Standard_v2,WAF_v2." Details=[]

I have faced same issue, while attempted to create AGW Standard tier (v1) and the configuration of this version AGW does not supports the argument "priority". That is mandatory for all AGW tiers, but shoud be mandatory only for tier Standard_v2 and WAF_v2. It's a blocker issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants