CI integration
Your pipeline already runs terraform plan and terraform apply. The CI integration sends
Aletheia the results, so the change timeline knows what your automation intended and what
it actually did.
What it sends
Section titled “What it sends”- Plans — the plan your pipeline generated, describing intended changes.
- Executions — the apply your pipeline ran, describing what actually happened.
What it does not do
Section titled “What it does not do”This integration is observational. It never runs terraform apply, never touches your
state, and holds no cloud credentials. Your pipeline runs Terraform exactly as it does
today and reports the outcome afterwards.
How it authenticates
Section titled “How it authenticates”You generate an ingest token under Administration and give it to your pipeline as a secret. The token is scoped to your organization and to ingest only — it cannot read your inventory, and it is not a user token. Revoke it at any time without affecting anyone’s login.
In this section
Section titled “In this section”- GitHub Actions — the ready-made action.
- Any CI — the ingest script, with recipes for GitLab CI, Jenkins, CodeBuild, and Atlantis.
- Ingest tokens — creating, scoping, and revoking them.
- Plans and executions — what Aletheia does with what you send.
Where to go next
Section titled “Where to go next”- Explore your infrastructure to see ingested plans and executions in context.
- API for the ingest endpoints in full.