Default origin healthcheck timeout seconds is too short

[ysugimoto]

Terraform Version

Terraform v1.7.1
on darwin_arm64

Affected Fastly Terraform Resource(s)

Please list the affected resources, for example:

• fastly_service_vcl.healthcheck

Terraform Configuration Files

healthcheck {
    name   = "example_healthcheck"
    host   = "example.com"
    path   = "/"
}

Expected Behavior

What should have happened?

When I create healthcheck setting without the timeout field, it's set as 500ms as default.
I think 500ms is too short to respond successfully between Fastly's edge and some regional origins.

On creating healthcheck setting via the managed console, the default timeout is 5s as default.
So I propose that this field also be 5000ms or bit extend as default in terraform.

Actual Behavior

What actually happened?

500ms is too short and some regional healthcheck may timeout and then Deliver service respond with 503 Backend Unhealthy.

Debug Output (optional)

Please provide a link to a GitHub Gist containing the complete debug output (see Terraform docs). Ensure any sensitive data is <REDACTED>.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply

Important Factoids (optional)

Is there anything atypical about your account or set up that we should know?

I'm using Fastly in Japan, and setting up a backend with Cloud Run as Asia regional.
When I accessed from Osaka Data Center and then Cloud Run will accept request in a Hongkong region, then it took over 500ms and timed out the HTTP request.