CLB health_check_type don't support PING

[newhandLiu]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

terraform -v Terraform v1.0.6 on darwin_amd64

• provider registry.terraform.io/tencentcloudstack/tencentcloud v1.59.8

Affected Resource(s)

• tencentcloud_clb_listener

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp
resource "tencentcloud_clb_listener" "echosvr" {
  clb_id                     = "lb-3qhrxe1v"
  listener_name              = "echosvr"
  port                       = 10000
  protocol                   = "UDP"
  target_type                = "NODE"
  health_check_switch        = true
  health_check_time_out      = 2
  health_check_interval_time = 5
  health_check_health_num    = 3
  health_check_unhealth_num  = 3
  health_check_type          = "PING" 
  health_check_context_type= "TEXT"
}

Debug Output

Error: "health_check_type" must contain a valid string value must in array []string{"CUSTOM", "TCP", "HTTP"}, got "PING"

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

1. terraform apply

Important Factoids

References

• 0000

[Kagashino]

Reference to Cloud API Document , the Health Check Type only available for TCP, HTTP and CUSTOM. Argument Validation here is consistent with the Cloud API.

[newhandLiu]

but it's supported in the console.

[Kagashino]

@newhandLiu Sorry to reply so late. We are planning to remove the validation of health check type and port. To learn about more details, recommend to submit a ticket to Cloud Load Balancer team to work out the reason of the inconsistent between console (your snapshot) and API constrait.