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

Application Gateway - sku.family set to 'Generation_2', deploys 'Generation_1' #2317

Open
kellybeazley opened this issue Oct 1, 2024 · 2 comments

Comments

@kellybeazley
Copy link

Bicep version
Bicep CLI version 0.30.23 (ec3612efc7)

Describe the bug
When deploying an application gateway with WAF_v2 and family set to 'Generation_2', it deploys 'Generation_1'
When running deployment again it shows the change to try and change from Generation_1 => Generation_2.
I am using the latest API: 'Microsoft.Network/applicationGateways@2023-11-01'

To Reproduce
Steps to reproduce the behavior:

Code configured with:
properties: {
sku: {
name: 'WAF_v2'
tier: 'WAF_v2'
family: 'Generation_2'
}

Additional context
image
image
image

@stephaniezyen
Copy link
Contributor

Unfortunately this is a Microsoft.Network issue, please open a support ticket with that team.

@stephaniezyen stephaniezyen transferred this issue from Azure/bicep Oct 9, 2024
@kellybeazley
Copy link
Author

@stephaniezyen where do I raise this exactly with the Microsoft.Network team?

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

No branches or pull requests

2 participants