An audit trail of HCP Terraform runs

A workspace's run list tells you what Terraform did in that workspace. It does not put the apply next to the alert that followed it, or next to the application deploy that went out at the same time. Kollaber records completed runs as timeline events so infrastructure changes sit alongside everything else that changed.

What lands on the timeline

Service
The workspace name.
Status
Applied as a success, errored as a failure.
Run detail
The run that produced the notification.

Setup

  1. 1Open the workspace notification settings

    In HCP Terraform, go to Settings, then Notifications, then Create a notification, and choose Webhook.

  2. 2Point it at Kollaber

    Use your environment UUID in the URL and your WEBHOOK_SECRET as the token.

    URL:      https://kollaber.io/webhooks/terraform?environment_id=<uuid>
Token:    your WEBHOOK_SECRET
Triggers: Completed, Errored

  3. 3Apply something

    The next completed run appears on the timeline, with the workspace as the service name.

Good to know

  • The token signs the body with HMAC-SHA512, which Kollaber verifies against WEBHOOK_SECRET. Deliveries that fail verification are rejected.
  • Only runs that reached your infrastructure are recorded: applied as a success, errored as a failure. Plan, cancel, and discard notifications are accepted and skipped, so enabling extra triggers is harmless — a plan is not a change, and recording one would add a timeline marker for a run that touched nothing and count it as a deployment in DORA.

Questions

Is it safe to enable every notification trigger?

Yes. Triggers that do not represent a change — plan, cancel, discard — are accepted and skipped rather than recorded, so nothing pollutes the timeline or the DORA figures.

How do workspaces map to environments?

The environment comes from the environment_id in the notification URL, so create one notification per workspace pointing at whichever environment it manages.

Does this work with self-managed Terraform Enterprise?

The webhook format is the same, so a Terraform Enterprise workspace configured with the same URL and token behaves identically.

Other integrations

GitHub ActionsArgo CDAtlantisPrometheus AlertmanagerKubernetes

Start recording HCP Terraform changes

The free plan covers two environments and five members. The full reference for this integration lives in the docs.

Get started freeAll integrations