Atlantis leaves its history in pull request comments, spread across repositories. Six weeks later, working out which apply changed a security group means searching GitHub. Kollaber records each apply as a timeline event with the pull request attached, so the change and its rationale stay together.
Atlantis posts webhooks from repos.yaml. Point the apply event at Kollaber with your environment UUID.
# repos.yaml
webhooks:
- event: apply
kind: http
url: https://kollaber.io/webhooks/atlantis?environment_id=<uuid>Atlantis cannot sign the body, so a shared secret in a static header is what it can offer. Set it on the server flag or the equivalent environment variable.
--webhook-http-headers='{"Authorization":"Bearer $WEBHOOK_SECRET"}'Atlantis posts only after an apply has run, so every delivery is a real change to your infrastructure.
No. The webhook is registered on the apply event only, and Atlantis posts it after the apply has run, so plans never reach the timeline.
The project name from atlantis.yaml is used when present. Without one it falls back to the directory, and then to the repository name.
Yes. Register multiple webhooks with different environment_id values and use workspace-regex or branch-regex to decide which applies go where.
The free plan covers two environments and five members. The full reference for this integration lives in the docs.