You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
Hi there, just trying to setup pingdom with terraform via the examples, and am getting an 403: invalid application key error.
I'm using a multi-user account and have generated an API key from Integrations -> The Pingdom API with read write access, but I'm thrown the error.
Note: The api_key works when I use curl with it, so I suspect the api_key isn't the invalid one
i.e curl -X GET https://api.pingdom.com/api/3.1/checks -H 'Authorization:Bearer <api_key>'
variable "pingdom_user" {}
variable "pingdom_password" {}
variable "pingdom_api_key" {}
variable "pingdom_account_email" {} # Optional: only required for multi-user accounts
provider "pingdom" {
user = "${var.pingdom_user}"
password = "${var.pingdom_password}"
api_key = "${var.pingdom_api_key}"
account_email = "${var.pingdom_account_email}" # Optional: only required for multi-user accounts
}
resource "pingdom_check" "example" {
type = "http"
name = "my http check"
host = "example.com"
resolution = 5
}
The text was updated successfully, but these errors were encountered:
Looks like this provider uses old version of Pingdom API (2.1 or older), so you have to use API key for old integrations, you can generate it here: https://my.pingdom.com/app/account/appkeys
Hi there, just trying to setup pingdom with terraform via the examples, and am getting an 403: invalid application key error.
I'm using a multi-user account and have generated an API key from Integrations -> The Pingdom API with read write access, but I'm thrown the error.
Note: The api_key works when I use curl with it, so I suspect the api_key isn't the invalid one
i.e
curl -X GET https://api.pingdom.com/api/3.1/checks -H 'Authorization:Bearer <api_key>'
The text was updated successfully, but these errors were encountered: