ALB target group defaults changed for healthy/unhealthy thresholds

[wvidana]

Hi,

So this commit changed the target group default parameters 79467dc

This makes old code to have pending changes, when there are non. (By old I mean code applied with aws provider <1.3 and revisited now on 1.6). Also the defaults mismatch with the official AWS API for Application Load Balancer.

Is it necessary to define here defaults? Not sure if the Go SDK can provide those or the API call can relay on leaving them empty. In example, the UnhealthyThresholdCount now is forced to be 3, when it used to be 2, and AWS official API defaults to 2 for ALB (though that gets tricky for network load balancers, which I guess was the reason of the change).

If there is no other way around it, I wouldn't mind on updating my module to force my own default, though I would rather relay on official's AWS defaults, which differs between ALB and NLB.

Terraform Version

Terraform v0.11.1
provider.aws: version = "~> 1.6"

Affected Resource(s)

• aws_alb_target_group

Expected Behavior

No code changes -> no terraform changes

Actual Behavior

terraform plan wants to make changes when there are no code changes.

References

• Introduced in 1.3.0 r/lb_target_group: fix compatibility with Network Load Balancers #2251
• AWS API Reference (API Version 2015-12-01) https://docs.aws.amazon.com/elasticloadbalancing/latest/APIReference/API_CreateTargetGroup.html

[wvidana]

This PR #2380 seems to fix it for matcher, path and timeout, though not for the healthy and unhealthy thresholds yet.

[github-actions]

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!

[ghost]

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!