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
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
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."
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
Apr 28, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: