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

There is no way to associate health checks with backend origin servers #18

Closed
dbeckham opened this issue Jul 11, 2017 · 1 comment
Closed

Comments

@dbeckham
Copy link
Contributor

Terraform Version

Terraform v0.9.11

Affected Resource(s)

  • fastly_service_v1

Terraform Configuration Files

resource "fastly_service_v1" "test" {
  name = "test"

  domain {
    name = "test.example.com"
  }

  backend {
    address          = "1.1.1.1"
    name             = "east"
    port             = 80
  }

  backend {
    address          = "2.2.2.2"
    name             = "west"
    port             = 80
  }

  healthcheck {
    name              = "beacon"
    host              = "test.example.com"
    path              = "/beacon.gif"
    method            = "HEAD"
    expected_response = 200
  }

}

Expected Behavior

There should be a parameter to allow a health check to be associated with a specific backend.

Actual Behavior

There is no way to associate a defined health check with a backend. The backend definitions in VCL end up being generated with no .probe = { } block. Health check definitions are effectively ignored.

Steps to Reproduce

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

  1. Define a fastly_service_v1 resource similar to the example above, and run terraform apply.
@dbeckham
Copy link
Contributor Author

I'm closing this as it's a documentation problem, not a code problem. PR #20 has fixes for the backend healthcheck docs.

phamann pushed a commit that referenced this issue Aug 10, 2020
waf configuration resource deletion implementation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant