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

Application Gateway independent resources #1893

Closed
OffColour opened this issue Sep 7, 2018 · 2 comments
Closed

Application Gateway independent resources #1893

OffColour opened this issue Sep 7, 2018 · 2 comments

Comments

@OffColour
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

From the Application Gateway, break out probe, http_listener, request_routing_rule and backend_http_setting as separate resources in line with the way the Load Balancer is implemented.
When running a multi site app gateway, these setting are heavily tied into the deployment of websites and would be useful to define away from the App Gateway itself and delegate to a DevOps team.

New or Affected Resource(s)

  • azurerm_ag_healthprobe

  • azurerm_ag_backend_http_settings

  • azurerm_ag_http_listener

  • azurerm_ag_ssl_certificate

  • azurerm_ag_request_routing_rule

  • #0000

@tombuildsstuff
Copy link
Contributor

hi @OffColour

Thanks for opening this issue :)

This feature request is blocked on the Azure API not supporting it at this time - however it's currently being tracked in #1576 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of #1576 - please subscribe to that for updates.

Thanks!

@ghost
Copy link

ghost commented Mar 6, 2019

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 Mar 6, 2019
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

2 participants