Command line triggers for Terraform

Command line triggers enable you to call a check from a CI/CD pipeline, a bash shell or programmatically in your code. You can specify command line triggers as standalone resources at check or group level:

resource "checkly_trigger_check" "test-trigger-check" {
   check_id = "c1ff95c5-d7f6-4a90-9ce2-1e605f117592"    // The id of the check to be triggered
}

output "test-trigger-check-url" {
  value     = checkly_trigger_check.test-trigger-check.url  // This will output the trigger url
  sensitive = true
}

resource "checkly_trigger_group" "test-trigger-group" { // The id of the group to be triggered
   group_id = "215"
}

output "test-trigger-group-url" {
  value     = checkly_trigger_group.test-trigger-group.url  // This will output the trigger url
  sensitive = true
}

The trigger url and token contain a secret token, so the Checkly provider marks them as sensitive and Terraform requires any output that references them to set sensitive = true. Sensitive outputs are hidden in terraform plan and terraform apply output; read the value with terraform output -raw test-trigger-check-url. You can see all the configuration options for group triggers, as well as more examples check triggers, on the official Terraform registry documentation page.

Getting Started

Detect

Communicate

Resolve

AI

Integrations

Command line triggers for Terraform