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

Optional Variable called "availability_zone" under "frontend_ip_configuration" for the resource "azurerm_lb" is actually a Required variable now #12286

Closed
binoyjt opened this issue Jun 19, 2021 · 4 comments

Comments

@binoyjt
Copy link

binoyjt commented Jun 19, 2021

Under the resource "azurerm_lb" the "frontend_ip_configuration" has an optional setting. This setting is the Availability Zone. Terraform Fails if this Setting is not passed. For a LB with no AV Zone we need to pass a value called as "No-Zone" so that the apply is successful.

@WodansSon
Copy link
Collaborator

@binoyjt Thanks for opening this issue. I believe this issue has been fixed in #12208

@katbyte katbyte modified the milestones: v2.63.0, v2.64.0 Jun 23, 2021
@binoyjt
Copy link
Author

binoyjt commented Aug 3, 2021

Can the document be updated as this is a required variable and needs to be set at "No Zone" for regions with no AV Zones. Otherwise it fails.

@rcskosir
Copy link
Contributor

Thanks for opening this issue. This was a problem in the 2.x version of the provider which is no longer actively maintained.
If this is still an issue with the 3.x version of the provider please do let us know by opening a new issue, thanks!

@rcskosir rcskosir closed this as not planned Won't fix, can't repro, duplicate, stale Jul 28, 2023
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants