Update lb_listener datasource schema to match lb_listener default_action forward schema#17238
Conversation
…er resource schema
|
@gdavison I would be very grateful if you could take a look to this bugfix when you have a while, it is a very simple change that I think can be approved quickly. Thank you! 😄 |
bflad
left a comment
There was a problem hiding this comment.
Added a covering acceptance test. Thank you, @rdelcampog for this fix. 🚀
…7238 Output from acceptance testing: ``` --- PASS: TestAccDataSourceAWSLBListener_DefaultAction_Forward (1065.87s) ```
|
This has been released in version 3.26.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! |
|
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
Relates #12574
Relates #10942
Bug description
When the weighted target group functionality was added back in June 2020 in #12547, the lb_listener
default_actionblock schema was not updated.Affected Resource(s)
Expected Behavior
Terraform should retrieve the specified AWS ELB listener configuration object for cases where there is a single target group configured, or weighted target groups are used on the resource.
Actual Behavior
If the
aws_lb_listenerdatasource tries to retrieve a listener configured with a weighted target group forward default action:Terraform stops with an error:
Steps to Reproduce
Terraform Configuration Files
This bug prevents gathering the current weight configured in the default action of an AWS ALB listener, needed for example to detect the current Target Group ARN that is currently receiving the 100% of the traffic (very useful for active side detection in blue-green deployments):
Release note for CHANGELOG:
Output from acceptance testing: