For the complete documentation index, see llms.txt. This page is also available as Markdown.

Terraform

Keep teams, rotations, PagerDuty and Opsgenie syncs, escalation policies, alert integrations, services and group on-calls in Terraform, and let plan show anything changed by hand.

The Pagerly Terraform provider keeps your on-call configuration in code. Changes go through a pull request, CI applies them, and terraform plan shows anything someone changed in Slack or the dashboard. It works with Terraform and OpenTofu.

1. Create a key

An org admin opens MCP, API & Terraform in the dashboard's main menu, switches to the API Keys tab and clicks Generate API key. Store it in your CI secrets as PAGERLY_API_KEY. The key acts as the admin who created it.

2. Add the provider

terraform {
  required_providers {
    pagerly = {
      source  = "pagerly/pagerly"
      version = "~> 0.1"
    }
  }
}

provider "pagerly" {}   # reads PAGERLY_API_KEY

3. Describe a team

A team either runs a Pagerly rotation, or follows a schedule in PagerDuty, Opsgenie, Datadog, JSM Ops or Google Calendar.

People are email addresses, never Slack ids. A synced team's source must be connected under Scheduling Integrations first.

Already have teams?

The dashboard's Terraform tab lists an import block for every team. Paste them and run:

Terraform writes the matching configuration, and the plan shows nothing to change.

What else it manages

Escalation policies, alert integrations (with their webhook URL as an output), services, group on-calls and the user directory. Overrides, swaps and incidents stay in Slack and the dashboard.

The full reference, with an example for every resource, is at www.pagerly.io/docs/terraform.

Last updated