-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Support ALB Advanced Routing rules #8268
Conversation
Hey guys, is there anything I can do to help out here? Is there a target date for release for this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The format is acceptable and it would help on future changes if more conditions are added, or more details are required to be included in the specific condition type blocks 👍
@bflad do we have an estimate on when this may be reviewed/included for a release?
@allanhahn: Any idea when it will be released? |
@allanhahn any updates on when this feature is going to be release? |
Any updates on when this feature will be released? This would be really helpful. CC: @allanhahn |
Great work - our organization would definitely use this. Can we please get it merged in? |
Really want multi values in a condition:
Please add |
is this going to be merged soon? |
@bflad is this somehow missed? This is really crucial for us. |
Merge it please. |
The only "workaround" right now is creating Please, merge! |
@bflad is there any estimate on when will this PR merged ? We are really waiting for this feature. |
Please @bflad @ewbankkit @nywilken could you take some time to review this PR and comment it if something needs to be changed ? |
Hi Everyone! Is there any ETA on review and merge of this PR? |
Could you please merge this PR? This is an important future for us. |
@bflad would it be feasible to merge this PR anytime soon? Echoing the sentiment of many commentators in this thread, this addition would help me fully terraform my ALB requirements. Thank you for your time and effort. Cheers! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much! 🚀 🎉
--- PASS: TestAccAWSLBListenerRule_conditionQueryString (190.50s)
--- PASS: TestAccAWSLBListenerRule_conditionMultiple (201.69s)
--- PASS: TestAccAWSLBListenerRule_conditionHostHeader_deprecated (202.03s)
--- PASS: TestAccAWSLBListenerRule_changeListenerRuleArnForcesNew (203.73s)
--- PASS: TestAccAWSLBListenerRule_Action_Order_Recreates (204.14s)
--- PASS: TestAccAWSLBListenerRule_fixedResponse (206.32s)
--- PASS: TestAccAWSLBListenerRule_conditionHostHeader (208.64s)
--- PASS: TestAccAWSLBListenerRule_conditionPathPattern (210.67s)
--- PASS: TestAccAWSLBListenerRule_oidc (220.87s)
--- PASS: TestAccAWSLBListenerRule_conditionHttpHeader (226.07s)
--- PASS: TestAccAWSLBListenerRule_conditionPathPattern_deprecated (227.85s)
--- PASS: TestAccAWSLBListenerRule_conditionHttpRequestMethod (238.79s)
--- PASS: TestAccAWSLBListenerRuleBackwardsCompatibility (237.24s)
--- PASS: TestAccAWSLBListenerRule_Action_Order (251.73s)
--- PASS: TestAccAWSLBListenerRule_basic (268.04s)
--- PASS: TestAccAWSLBListenerRule_cognito (299.88s)
--- PASS: TestAccAWSLBListenerRule_redirect (299.05s)
--- PASS: TestAccAWSLBListenerRule_conditionSourceIp (309.71s)
--- PASS: TestAccAWSLBListenerRule_updateRulePriority (273.67s)
--- PASS: TestAccAWSLBListenerRule_priority (389.79s)
This will be included in next week's release, v2.42.0. |
Wonderful! Thank you @aeschright . |
@dpiddockcmp @aeschright Thank You for all your work on this! ❤️ |
Awesome! Thank you all!! |
Wow. Don't believe in it. Finally! |
Thanks, finally its merged. Was waiting for this from long time. |
will this have the new weighted target group feature? |
Hi @sandangel, This PR has been merged and no further changes will be made to it. Target group weighting is a feature of the forward Action. This PR was only adding the advanced routing rules which are part of the Conditions. Weighting would never have been added to this PR even if the feature had been released when this PR was being written. Issue #10942 has been raised for weighted target groups but no PR so far. |
This has been released in version 2.42.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
Upstream change: hashicorp/terraform-provider-aws#8268 Should fix this warning: ``` Warning: "condition.0.values": [DEPRECATED] use 'host_header' or 'path_pattern' attribute instead on .terraform/modules/atlantis/terraform-aws-modules-terraform-aws-atlantis-e1242e3/main.tf line 213, in resource "aws_lb_listener_rule" "redirect_http_to_https": 213: resource "aws_lb_listener_rule" "redirect_http_to_https" { ```
This reverts commit ed2b1b2.
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. Thanks! |
Community Note
Fixes #8126
Changes proposed in this pull request:
condition.field
andcondition.values
keys and deprecate themOutput from acceptance testing:
Notes
conditions custom hasher:
condition.values
and the applicable config block are set whencondition.field
ishost-header
orpath-pattern
.condition.field
andcondition.values
to config block. Users do not see a Diff on every plan.condition.field
andcondition.values
attributes.