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

deregistration_delay in aws_lb_target_group are not working if set to 0 #4035

Closed
fangli opened this issue Apr 4, 2018 · 2 comments
Closed

Comments

@fangli
Copy link

fangli commented Apr 4, 2018

Not a native English speaker, sorry for any grammatical mistakes:)

Terraform Version:
Terraform v0.11.4

  • provider.aws v1.13.0

Resource: aws_lb_target_group
Parameter: deregistration_delay

Description:
Param deregistration_delay could be set to 0 in AWS web console, which means disable deregistration delay.
But if I set this param to 0 in terraform, the created target group has a 300s deregistration delay, which is the default value in AWS webconsole.

Expected Behavior: 0s of deregistration delay
Actual Behavior: 300s of deregistration delay

This ONLY happens when new targetgroup creation. In case of updating or changing, this parameter works good.

Configuration:

resource "aws_lb_target_group" "target_group_80" {
  name = "${var.project}-${var.environment}-${var.service}-80"
  port     = 80
  protocol = "TCP"
  deregistration_delay = 0
  target_type = "instance"
  vpc_id   = "${var.vpc_id}"

  health_check {
    interval = 10
    protocol = "HTTP"
    path = "/"
    port = 80
    healthy_threshold = 2
    unhealthy_threshold = 2
  }

  tags {
    Name = "${var.project}-${var.environment}-${var.service}"
    project = "${var.project}"
    environment =  "${var.environment}"
    service =  "${var.service}"
  }

}

#3152

@catsby
Copy link
Contributor

catsby commented Apr 5, 2018

Closing as duplicate of #3152, thanks for writing in!

@catsby catsby closed this as completed Apr 5, 2018
@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
None yet
Projects
None yet
Development

No branches or pull requests

2 participants