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

resource_arm_application_gateway is missing zone #2293

Closed
KZachariassen opened this issue Nov 12, 2018 · 2 comments · Fixed by #3144
Closed

resource_arm_application_gateway is missing zone #2293

KZachariassen opened this issue Nov 12, 2018 · 2 comments · Fixed by #3144

Comments

@KZachariassen
Copy link

When you create a application_gateway using WAF_V2 sku you should be able to set availability zone, this is not possible. This is how it looks in powershell

$appgw = New-AzureRmApplicationGateway -Name "AutoscalingAppGw" -Zone 1,2,3 `
  -ResourceGroupName $rg -Location $location -BackendAddressPools $pool `
  -BackendHttpSettingsCollection $setting -GatewayIpConfigurations $ipconfig `
  -FrontendIpConfigurations $fip -FrontendPorts $fp01, $fp02 `
  -HttpListeners $listener01, $listener02 -RequestRoutingRules $rule01, $rule02 `
  -Sku $sku -sslCertificates $sslCert01 -AutoscaleConfiguration $autoscaleConfig
@KZachariassen
Copy link
Author

If I create the object with powershell and import the object into State and then try to modify it, I get this:

application-gateway has an existing availability zone constraint 1, 2, 3 and the request has availability zone constraint , which do not match. Zones cannot be added/updated/removed once the resource is created."

@ghost
Copy link

ghost commented Apr 28, 2019

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 ghost locked and limited conversation to collaborators Apr 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants