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

provider/azurerm: currently lacking load balancer resource #8007

Closed
pmcatominey opened this issue Aug 5, 2016 · 5 comments
Closed

provider/azurerm: currently lacking load balancer resource #8007

pmcatominey opened this issue Aug 5, 2016 · 5 comments

Comments

@pmcatominey
Copy link
Contributor

Hi,

I'm creating this issue as a feature request and central discussion point for load balancer support in the azurerm provider.

There are a number of PR's open, proposing solutions:

The latter two are attempts to providing the resource in different ways to the first. It would be good to hear thoughts on what solution is preferred and get the ball rolling again.

Personally I am in favour of having separated resources to model in particular the probes and rules, at least until it is possible to pass multiple sets into a module of the same type.

Regards

@jen20
Copy link
Contributor

jen20 commented Aug 6, 2016

Hi @pmcatominey! I agree that in the short term (until nested resources are implemented) that we should model each load balancer component as an independent resource. One of the team will pick up one of open proposals at some point soon now that 0.7 is out the door.

@edevil
Copy link
Contributor

edevil commented Sep 13, 2016

Should we follow this ticket or #8130 for the status of load balancer support in the AzureRM module?

@zachgersh
Copy link
Contributor

zachgersh commented Sep 21, 2016

hey @jen20 - could we just pour a tiny bit more time or even just merge #6467? It would seem that this is the split resource approach that you were wanting (and I agree is a better approach). It would be super disappointing if we had to wait even longer to get even rudimentary LB support for azure as a whole handful of these PRs have been open for quite a few months without a definitive direction. cc @stack72

As a side note - I would be happy to contribute to fixing any other issues that are needed to get that LB support merged.

@stack72
Copy link
Contributor

stack72 commented Oct 3, 2016

Hi @pmcatominey

This is going to be seen through to completion by @jen20 and I in #9199

Paul

@stack72 stack72 closed this as completed Oct 3, 2016
@ghost
Copy link

ghost commented Apr 21, 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 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.

@ghost ghost locked and limited conversation to collaborators Apr 21, 2020
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

5 participants