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

azurerm_application_gateway request_routing_rule missing redirection configuration #1326

Closed
robsonpeixoto opened this issue May 31, 2018 · 2 comments

Comments

@robsonpeixoto
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

Add a feature to configure redirection from a Listener to another Listener. Really useful to implement redirect from http to https

New or Affected Resource(s)

  • azurerm_application_gateway.*.request_routing_rule

Potential Terraform Configuration

...
  request_routing_rule {
    name                 = "http-to-https-rule"
    rule_type            = "Basic"
    redirect             = true
    from_listener        = "http-listener"
    configure_redirect   = true
    redirect_type        = "Permanent"          # options: ["Permanent", "Temporary", "Found", "SeeOther"]
    target_listener      = "https-listener"
    include_query_string = true
    include_path         = true
  }
...

References

https://docs.microsoft.com/en-us/azure/application-gateway/tutorial-http-redirect-powershell

@tombuildsstuff
Copy link
Contributor

hey @robsonpeixoto

Thanks for opening this issue :)

Support for this has previously been requested in #552 which I'm going to close this issue in favour of. Unfortunately at the moment we're blocked on a bug in the Application Gateway API which needs to be fixed before we extend this resource (but is apparently being deployed in the near future; there's additional details in the other issue)

Thanks!

@ghost
Copy link

ghost commented Mar 31, 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 Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants