azurerm_lb: allow ipv6 addresses for the private_ip_address property
#6125
Conversation
katbyte
changed the title
There was a problem hiding this comment.
Hi @fabianofranz,
Is the issue that the ip address can be ipv4 or ipv6? if that is the case could we change the validation to accept either rather then any string?
The azure load balancer resource's frontend_ip_configuration argument assumes the IP address is only going to be IPv4. This removes that restriction to be in line with the rest of the terraform code that does not have that validation.
Done, changed to either accept IPv4, IPv6, or empty. |
|
@katbyte ^ |
katbyte
changed the title
private_ip_address property
|
@katbyte looks good, thanks! |
|
This has been released in version 2.3.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.3.0"
}
# ... other configuration ... |
|
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 👉 [email protected]. Thanks! |
ghost
locked and limited conversation to collaborators
The azure load balancer resource's frontend_ip_configuration argument assumes
the IP address is only going to be IPv4. This removes that restriction to be
in line with the rest of the terraform code that does not have that validation.