-
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
[Bug]: aws_lb_listener is refreshing not quite correct #32983
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Related to #22526 |
This functionality has been released in v5.36.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. Thank you! |
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. |
Terraform Core Version
1.5.5
AWS Provider Version
5.12.0
Affected Resource(s)
aws_lb_listener
Expected Behavior
I've created alb listener by code:
That is there is configuration block "forward" with subblock "stickiness". It's confirming by aws cli:
And AWS console:
Actual Behavior
I've got in state file:
That is configuration block "forward" is empty. Accordingly, this leads to an update listener every apply.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
alb.zip
Steps to Reproduce
unzip alb.zip
terraform workspace new cloud3
terraform init
terraform apply
terraform apply
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: