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

Fixes #628 - multiple output IPs for azurerm_lb #633

Merged
merged 5 commits into from
Dec 18, 2017

Conversation

tevert
Copy link
Contributor

@tevert tevert commented Dec 14, 2017

This PR changes the azurerm_lb resource to output a list of private IPs instead of just the first one, to improve support for load balancers with multiple IP configurations.

@tevert tevert changed the title Fixes #628 Fixes #628 - multiple output IPs for azurerm_lb Dec 14, 2017
@tombuildsstuff tombuildsstuff added this to the 1.0.1 milestone Dec 14, 2017
Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @tevert

Thanks for this PR - I've taken a look through and this mostly LGTM. However in order to maintain compatibility for users already using this field can we update this to set the private_ip_address field (in addition to the new private_ip_addresses field?

Thanks!

@tevert
Copy link
Contributor Author

tevert commented Dec 14, 2017

That makes sense; I've added the old one back in

Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @tevert

Thanks for pushing the latest changes - this LGTM 👍

Thanks!

@tombuildsstuff
Copy link
Contributor

Tests pass:

screen shot 2017-12-18 at 07 41 05

@tombuildsstuff tombuildsstuff merged commit 867f40a into hashicorp:master Dec 18, 2017
tombuildsstuff added a commit that referenced this pull request Dec 18, 2017
@ghost
Copy link

ghost commented Apr 1, 2020

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

Successfully merging this pull request may close these issues.

2 participants