Skip to content
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

aws_lb resource enable_http2 for network type load balancer doesn't make sense (and is invalid) #4011

Closed
tpickett66 opened this issue Apr 2, 2018 · 3 comments · Fixed by #4032
Labels
service/elbv2 Issues and PRs that pertain to the elbv2 service.
Milestone

Comments

@tpickett66
Copy link

After updating from 1.10 to 1.13 an unexpected change to my NLB is trying to be made.

Terraform Version

» terraform -v
Terraform v0.11.5
+ provider.aws v1.13.0

Affected Resource(s)

  • aws_lb

Terraform Configuration Files

resource "aws_lb" "my-lb" {
  name_prefix        = "my-lb"
  load_balancer_type = "network"
}

Expected Behavior

I expected the network type LB to not default to enabling http2.

Actual Behavior

The new default attempted to enable http2 for a network type load balancer.

Steps to Reproduce

  1. Provision a load balancer of type "network" using a v1.10 of the provider
  2. Update to 1.13 of the provider
  3. Run terraform plan and note the addition of the new default.
@bflad bflad added the service/elbv2 Issues and PRs that pertain to the elbv2 service. label Apr 2, 2018
@bflad bflad added this to the v1.14.0 milestone Apr 4, 2018
@bflad
Copy link
Contributor

bflad commented Apr 4, 2018

The attributes have had a DiffSuppressFunc added via #4032, which was merged into master and will release with v1.14.0 of the AWS provider, likely by the end of the week.

@bflad
Copy link
Contributor

bflad commented Apr 6, 2018

This has been released in version 1.14.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

@ghost
Copy link

ghost commented Apr 6, 2020

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!

@ghost ghost locked and limited conversation to collaborators Apr 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/elbv2 Issues and PRs that pertain to the elbv2 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants