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

aws_listener_rule forwarding using http request methods #8315

Closed
Richard-Prince opened this issue Apr 15, 2019 · 4 comments
Closed

aws_listener_rule forwarding using http request methods #8315

Richard-Prince opened this issue Apr 15, 2019 · 4 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@Richard-Prince
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

When creating an aws alb listener rule, you cannot forward based on http request method rules.
I.E.
GET example.com/items forwards to target group A
POST example.com/items forwards to target group B

It would also be useful to use this in combination with already existing conditions, routing based on path and request method

New or Affected Resource(s)

  • aws-listener-rule

Potential Terraform Configuration

resource "aws_lb_listener_rule" "main" {
  listener_arn = "${var.listner-arn}"
  priority     = "${var.priority}"

  action {
    type             = "${var.action-type}"
    target_group_arn = "${var.action-target_group_arn}"
  }

  condition {
    method = "POST"
    field  = "${var.condition-field}"
    values = ["${var.condition-value}"]
  }
}
@Richard-Prince Richard-Prince added the enhancement Requests to existing resources that expand the functionality or scope. label Apr 15, 2019
@sunilkumarmohanty
Copy link
Contributor

Looks like this was fixed in #8268

@ewbankkit
Copy link
Contributor

Yes, I think this is a duplicate of #8126.

@github-actions
Copy link

github-actions bot commented Apr 5, 2021

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 5, 2021
@github-actions github-actions bot closed this as completed May 6, 2021
@github-actions
Copy link

github-actions bot commented Jun 6, 2021

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

3 participants