[Bug]: Fixed-Response `aws_lb_listener_rule` Always Shows Spurious `+ condition {}` Diff

[jamiejackson]

Terraform Core Version

1.8.3

AWS Provider Version

5.58.0

Affected Resource(s)

• aws_lb_listener_rule

Expected Behavior

Applying plan diffs should result in no more plan diffs. This is especially important as we have drift detection pipelines enabled, which fail when there are diffs.

Actual Behavior

Terraform always thinks that condition {} should be added.

Relevant Error/Panic Output Snippet

Terraform will perform the following actions:

  # aws_lb_listener_rule.test4_hudexchange_info__https__default will be updated in-place
  ~ resource "aws_lb_listener_rule" "test4_hudexchange_info__https__default" {
        id           = "arn:aws:elasticloadbalancing:us-east-1:063649415520:listener-rule/app/dev-elb/4f0bf3674f68865f/5d0e9f172dd7ed5c/f8ca34c4a6d7f43a"
        tags         = {}
        # (4 unchanged attributes hidden)

      + condition {}

        # (1 unchanged block hidden)
    }

Terraform Configuration Files

resource "aws_lb_listener_rule" "test4_hudexchange_info__https__default" {
  listener_arn = aws_lb_listener.test4_hudexchange_info__https.arn
  priority     = 99999
  tags         = {}
  action {
    order = 1
    type  = "fixed-response"
    fixed_response {
      content_type = "text/plain"
      message_body = "Host not recognized."
      status_code  = jsonencode(503)
    }
  }
  condition {}
}

Steps to Reproduce

plan, apply, repeat.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.