In the previous subchapter, we set up a basic pipeline with GitHub Actions. It works very well, but there are specialized tools for the Terraform workflow that make it even more convenient and secure. The most well-known is Atlantis. In this subchapter, you'll understand what it brings to the table and why many teams adopt it to take their infrastructure GitOps to the next level.

We saw the concept of GitOps in subchapter 12.5: managing infrastructure through Git and Pull Requests, so that every change is proposed, reviewed, and applied via the Git workflow. Atlantis is a tool designed specifically to do GitOps with Terraform as smoothly as possible.

Atlantis is an open source tool that automates Terraform directly from Pull Requests, via comments. Instead of the pipeline running plan and apply "on its own," with Atlantis you and your team control those actions by writing comments in the PR itself.

Analogy: Atlantis is like an assistant that lives inside your Pull Requests. You give it commands via comments ("plan this," "apply it") and it executes them and replies right there, leaving everything recorded in the PR conversation. It's like having Terraform "embedded" in the change discussion.

The typical workflow is very natural and conversational:

Everything happens inside the Pull Request: the plan, the review, the approval, and the apply are all recorded in one place, like a conversation. It's total traceability and very easy to follow.

You could do something similar with GitHub Actions (subchapter 22.1), so what advantages does Atlantis have?

Atlantis "understands" Terraform: it manages plan and apply, state, locks, workspaces... natively. You don't have to build all that logic by hand in a generic pipeline.

Atlantis automatically posts the plan as a comment, perfectly integrating it into the review. The "safety net" of reviewing the plan (subchapter 12.5) is built in by default.

You decide when to apply, writing atlantis apply only when everything is reviewed and approved. It gives explicit and deliberate control over the deployment moment.

Atlantis adds smart locking: if a PR is "working" on certain infrastructure, it blocks another PR from touching the same thing at the same time. This complements state locking (subchapter 20.2) by preventing conflicts between simultaneous changes, right from the review phase.

An important practical difference: Atlantis is an application that you have to run and maintain yourself (usually on a server or container within your infrastructure). It's not a service you "just use" like GitHub Actions. This gives you more control and privacy (your code and credentials never leave your environment), but also means maintenance responsibility.

Tip: as with other tools (remember Kubernetes in Chapter 17, or Terragrunt in 19.3), don't adopt Atlantis just because it's popular. Start with a simple pipeline. If your team grows and the GitOps workflow with Terraform becomes central to your daily work, Atlantis adds a lot. Choose based on real need.

• Atlantis is an open source tool that automates Terraform directly from Pull Requests, controlled via comments (atlantis plan, atlantis apply). Like an "assistant inside the PR."
• The workflow is conversational and everything is recorded in the PR: Atlantis runs the plan automatically, the team reviews it, it's approved, and someone comments atlantis apply to deploy.
• It brings advantages over a generic pipeline: designed for Terraform, the plan always visible in the PR, control via comments, and locking at the PR level.
• Unlike GitHub Actions, you host and maintain Atlantis (more control and privacy, but more responsibility).
• Don't adopt it because it's trendy: start simple and switch to Atlantis if GitOps with Terraform becomes central for your team.

In the next subchapter, we'll look at the "managed" option that avoids maintaining tools: Terraform Cloud / HCP Terraform, HashiCorp's own service.