CI and orchestrators

Infrastructure as a Database works under the tools that already run your Terraform: GitHub Actions, GitLab CI, Atlantis, Spacelift, or another CI system. Your tool still triggers and approves runs. The stategraph CLI plans and applies, and Stategraph holds the state, with scoped plans, per-resource conflict detection, and SQL over all your infrastructure.

Available integrations

• GitHub Actions: plan on pull requests, apply on merge, with a sticky comment.
• GitLab CI: plan on merge requests, apply on merge, with a sticky note.
• Atlantis: keep comment-driven pull request automation, with two run steps for Stategraph.
• Spacelift: run Stategraph through the Spacelift custom workflow tool.

Other CI systems, such as Jenkins or CircleCI, use the same steps as GitHub Actions and GitLab CI, with no integration. Export the three STATEGRAPH_* variables, and replace terraform plan and terraform apply with stategraph plan and stategraph apply.

Stategraph Orchestration

Orchestration is the other way to run Terraform from pull requests. It plans each pull request, enforces policy and approvals, and applies on a comment or on merge, on your GitHub Actions or GitLab CI runners. You write no pipeline YAML. See Workflows. With engine: stategraph, it plans through Infrastructure as a Database: see Use with Orchestration.

Next Steps

• Setup: API keys, tenants, and state import.