-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Possible regression on resource azurerm_lb with plugin 1.8 #1470
Comments
hey @jcmaasb Thanks for opening this issue :) That appears to be a regression in v1.8 of the AzureRM Provider, since it should be possible to set this value to an empty string. We’ll include a fix for this in the next release of the AzureRM provider - apologies for the inconvenience here! Thanks! |
Thank you very much for your quick reply! |
I think we have similar problem with subnet_id not specified in fronted_ip_configuration using Azurerm loadbalancer module:
|
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! |
I use this simple code in a module.
With plugin 1.7 it works fine, but with plugin 1.8 it generates this error if you set private_ip_address_allocation to dynamic and leave private_ip_address empty ("").
Error: module.ambari_MN.azurerm_lb.lb_private: "frontend_ip_configuration.0.private_ip_address" is not a valid IP4 address: ""
My question is whether this situation is final with the plugin1.8 (and I need to duplicate the code once more) or if it is a regression.
Thanks
The text was updated successfully, but these errors were encountered: