Atlantis Integration

DriftWise integrates with Atlantis via a run step in your workflow. No plugins, no sidecars.

Setup

Add the DriftWise step after plan in your atlantis.yaml:

atlantis.yaml

workflows:
  default:
    plan:
      steps:
        - init
        - plan
        - run: |
            terraform show -json $PLANFILE > /tmp/dw-plan.json
            curl -sX POST https://app.driftwise.ai/api/v2/orgs/$ORG_ID/analyze \
              -H "x-api-key: $DRIFTWISE_API_KEY" \
              -H "Content-Type: application/json" \
              -d "{\"plan_json\": $(cat /tmp/dw-plan.json | jq -Rs .)}"

Why the conversion step?

Atlantis's $PLANFILE is a binary Terraform plan. The terraform show -json step converts it to JSON, then jq -Rs wraps it as an escaped JSON string inside the plan_json field that the API expects.

Environment Variables

Set these in your Atlantis server environment:

Variable	Description
DRIFTWISE_API_KEY	Your DriftWise API key (dw2_...)
ORG_ID	Your DriftWise organization ID (UUID)

How It Works

1. Atlantis runs terraform plan as usual
2. The run step converts the binary plan to JSON and sends it to DriftWise
3. DriftWise analyzes the plan, scores risk, and returns a JSON response with the narrative
4. Atlantis includes the output in the plan result shown on the PR

Optional: CI Metadata

You can pass CI context so DriftWise can link the analysis back to the PR:

- run: |
    terraform show -json $PLANFILE > /tmp/dw-plan.json
    curl -sX POST https://app.driftwise.ai/api/v2/orgs/$ORG_ID/analyze \
      -H "x-api-key: $DRIFTWISE_API_KEY" \
      -H "Content-Type: application/json" \
      -d "{
        \"plan_json\": $(cat /tmp/dw-plan.json | jq -Rs .),
        \"ci\": {
          \"repo_owner\": \"$BASE_REPO_OWNER\",
          \"repo_name\": \"$BASE_REPO_NAME\",
          \"pr_number\": $PULL_NUM,
          \"commit_sha\": \"$HEAD_COMMIT\",
          \"branch\": \"$HEAD_BRANCH_NAME\"
        }
      }"