terraform-provider-pingdom

This project is a terraform provider for pingdom.

This currently only supports working with basic HTTP and ping checks.

Build and install

Using released versions

Prebuild releases for most platforms are available here. Download the release corresponding to your particular platform and place in $HOME/.terraform.d/plugins/registry.terraform.io/hashicorp/pingdom/[VERSION]/[os]_[arch]. For instance on Linux AMD64 the path would be $HOME/.terraform.d/plugins/registry.terraform.io/hashicorp/pingdom/1.0.0/linux_amd64.

After copying the plugin run terraform init in your projects that use this provider.

Put your v3 API key in the PINGDOM_API_TOKEN environment variable.

Dependencies for building from source

If you need to build from source, you should have a working Go environment setup. If not check out the Go getting started guide.

This project uses Go Modules for dependency management. To fetch all dependencies run go get inside this repository.

Build

make build

The binary will then be available at _build/terraform-provider-pingdom_VERSION.

Install

make install

This will place the binary under $HOME/.terraform.d/plugins/OS_ARCH/terraform-provider-pingdom_VERSION. After installing you will need to run terraform init in any project using the plugin.

Usage

Put your v3 API key in the PINGDOM_API_TOKEN environment variable or pass it to the provider in the api_key parameter.

Basic Check

provider "pingdom" {}

resource "pingdom_check" "example" {
    type = "http"
    name = "my http check"
    host = "example.com"
    resolution = 5
}

resource "pingdom_check" "example_with_alert" {
    type = "http"
    name = "my http check"
    host = "example.com"
    resolution = 5
    sendnotificationwhendown = 2
    integrationids = [
      12345678,
      23456789
    ]
    userids = [
      24680,
      13579
    ]
}

resource "pingdom_check" "ping_example" {
    type = "ping"
    name = "my ping check"
    host = "example.com"
    resolution = 1
    userids = [
      24680
    ]
}

Apply with:

 terraform apply \
    -var 'pingdom_api_key=YOUR_API_KEY'

Using attributes from other resources

variable "heroku_email" {}
variable "heroku_api_key" {}

variable "pingdom_api_key" {}

provider "heroku" {
    email = "${var.heroku_email}"
    api_key = "${var.heroku_api_key}"
}

provider "pingdom" {
    api_key = "${var.pingdom_api_key}"
}

resource "heroku_app" "example" {
    name = "my-app"
    region = "us"
}

resource "pingdom_check" "example" {
    name = "my check"
    host = "${heroku_app.example.heroku_hostname}"
    resolution = 5
}

Resources

Pingdom Check

Common Attibutes

The following common attributes for all check types can be set:

• name - (Required) The name of the check

• host - (Required) The hostname to check. Should be in the format example.com.

• resolution - (Required) The time in minutes between each check. Allowed values: (1,5,15,30,60).

• type - (Required) The check type. Allowed values: (http, ping).

• sendnotificationwhendown - The number of consecutive failed checks required to trigger an alert. Values of 0 are ignored.

• notifyagainevery - Notify again after n results. A value of 0 means no additional notifications will be sent.

• notifywhenbackup - Notify when backup.

• integrationids - List of integer integration IDs (defined by webhook URL) that will be triggered by the alerts. The ID can be extracted from the integrations page URL on the pingdom website.

• userids - List of integer user IDs that will be notified when the check is down.

• teamids - List of integer team IDs that will be notified when the check is down.

HTTP specific attibutes

For the HTTP checks, you can set these attributes:

• url - Target path on server.

• encryption - Enable encryption in the HTTP check (aka HTTPS).

• port - Target port for HTTP checks.

• username - Username for target HTTP authentication.

• password - Password for target HTTP authentication.

• shouldcontain - Target site should contain this string.

• shouldnotcontain - Target site should NOT contain this string. Not allowed defined together with shouldcontain.

• postdata - Data that should be posted to the web page, for example submission data for a sign-up or login form. The data needs to be formatted in the same way as a web browser would send it to the web server.

• requestheaders - Custom HTTP headers. It should be a hash with pairs, like { "header_name" = "header_content" }

• tags - List of tags the check should contain. Should be in the format "tagA,tagB"

• probefilters - Region from which the check should originate. One of NA, EU, APAC, or LATAM. Should be in the format "region:NA"

TCP specific attibutes

For the TCP checks, you can set these attributes:

• port - Target port for TCP checks.

• stringtosend - (optional) This string will be sent to the port

• stringtoexpect - (optional) This string must be returned by the remote host for the check to pass

The following attributes are exported:

• id The ID of the Pingdom check