Terraform Integration
Track every infrastructure change and automatically correlate Terraform applies with production anomalies. When something breaks after a deploy, TigerOps knows exactly which change caused it.
How It Works
Add the TigerOps Provider
Add the TigerOps Terraform provider to your root module. It runs as a null resource with no state — it simply posts events at plan and apply time.
Configure Your API Key
Set your TigerOps API key as a Terraform variable or environment variable. Works with Terraform Cloud, Terraform Enterprise, and open-source Terraform.
Every Apply Creates an Event
On each terraform apply, TigerOps receives a structured event with the workspace, operator, resource change summary, and plan metadata.
AI Correlates Changes to Anomalies
The AI SRE overlays apply events on your metrics timeline. When an anomaly follows a change, it surfaces the correlation immediately in incident reports.
What You Get Out of the Box
Deploy Event Timeline
Every terraform apply is annotated on your TigerOps dashboards as a deployment event — making it trivial to see if a change caused a metric regression.
Resource Change Summary
TigerOps records the number of resources added, changed, and destroyed per apply — giving AI context for why your infrastructure looks different.
Drift Detection Alerts
When your live infrastructure diverges from your Terraform state, TigerOps fires an alert — catching manual changes and runbook mistakes before they cause incidents.
Multi-Workspace Support
Track applies across all your Terraform workspaces — production, staging, and regional — in a unified view with workspace-level filtering.
Terraform Cloud Webhooks
For Terraform Cloud and Enterprise users, TigerOps can ingest workspace run events via native webhooks — no provider code required.
AI-Powered Change Risk Scoring
Before applying, TigerOps scores the blast radius of a planned change based on historical correlation between similar changes and past incidents.
Terraform Provider Setup
Add two blocks to your root module to start sending apply events to TigerOps.
# main.tf — TigerOps Terraform Integration
terraform {
required_providers {
tigerops = {
source = "tigerops/tigerops"
version = "~> 1.0"
}
}
}
provider "tigerops" {
api_key = var.tigerops_api_key
}
variable "tigerops_api_key" {
description = "TigerOps API key"
type = string
sensitive = true
}
# Emit a deployment event on every apply
resource "tigerops_deployment_event" "apply" {
service = "infrastructure"
environment = terraform.workspace
version = var.app_version
metadata = {
operator = var.operator
repo = "github.com/acme/infra"
workspace = terraform.workspace
}
}
# Usage: set TIGEROPS_API_KEY in your environment or CI secrets
# TF_VAR_tigerops_api_key=<your_key> terraform applyCommon Questions
Does TigerOps need to access my Terraform state files?
No. TigerOps does not read your Terraform state files. The integration works by posting change events (apply summaries) to the TigerOps API at apply time. No infrastructure secrets or state data are transmitted.
Does this work with Terraform Cloud and Terraform Enterprise?
Yes. For Terraform Cloud and Enterprise, you can use native workspace run webhooks to send events to TigerOps without modifying any .tf files. For open-source Terraform, the TigerOps provider handles event posting.
Can TigerOps help me correlate a Terraform apply with a production incident?
Yes. When a Terraform apply event is recorded, the AI SRE automatically watches the next 15 minutes of metrics for anomalies. If error rates, latency, or infrastructure metrics change after the apply, the AI surfaces the correlation in the incident timeline.
What information is captured per Terraform apply?
TigerOps captures: workspace name, operator (user or CI job), timestamp, Terraform version, number of resources added/changed/destroyed, plan status (success or error), and optional custom tags you add via variables. No resource attribute values or secrets are captured.
Does TigerOps support OpenTofu as well?
Yes. The TigerOps provider is compatible with OpenTofu (the open-source Terraform fork) in addition to HashiCorp Terraform. The same configuration works for both.
Know When Your Infra Breaks
No credit card required. Two lines of HCL. Instant change correlation.