All Tools View Categories About Contact Privacy

Terraform Atlantis Config Generator

Generate an atlantis.yaml with repos, projects and workflows.

Runs entirely in your browser - nothing is uploaded and no Atlantis server is contacted.
0
lines
0
characters
Your generated atlantis.yaml will appear here.

About Terraform Atlantis Config Generator

Atlantis is a popular open-source tool that automates Terraform via pull request comments in GitHub, GitLab and Bitbucket. Setting it up correctly means writing a server config, a repo-level atlantis.yaml, and the right workflow steps for plan and apply, plus wiring authentication and webhooks. The moving parts are numerous, and a small mistake in the repo config can leave plans running against the wrong directory or workspace, or approvals misapplied to the wrong environment entirely without anyone noticing until it is too late.

The Terraform Atlantis Pipeline Generator builds those configuration files for you. Tell it your VCS, the workflow steps you want, whether to use workspaces, and how to authenticate, and the tool emits a server config and a matching atlantis.yaml. It follows Atlantis conventions for project layout, autoplan, and workflow naming, so the output is close to runnable. Everything is generated in your browser with no upload and no connection to your VCS, keeping tokens and repo details private while you design the integration and iterate on it locally first.

Use it to bootstrap a new Atlantis install, to standardise repo configs across many repositories, or to produce a review-ready starting point your platform team can harden with secrets and policies before it goes live in production.

Because the output is plain text, your platform team can review the generated configuration in the same pull request as the modules it manages, keeping infrastructure automation and the code it runs side by side under the same review process and approval rules.

Features

  • Server config - a starting atlantis server configuration block you can extend.
  • Repo config - a matching atlantis.yaml for projects and workflows in the repo.
  • VCS options - GitHub, GitLab and Bitbucket settings to choose from in the form.
  • Workflows - custom plan and apply steps with extra commands included as needed.
  • Workspace support - per-directory or per-workspace layouts for isolation between teams.
  • Autoplan - when to auto-plan on pull request changes you configure explicitly.
  • Auth hints - notes for tokens and webhook secrets to fill in later from your vault.
  • Copy or download - export both config files together for convenient use.
  • Live stats - counts of projects and workflows defined in the generated output.
  • Private - config built locally only, never transmitted anywhere outside your machine.
  • Convention based - follows Atlantis norms so it runs as expected when deployed.
  • Review ready - output fits in a pull request for quick and easy sign-off.

How to Use

  1. Pick your VCS - GitHub, GitLab or Bitbucket as appropriate for your org.
  2. Describe projects - directories and workspaces to manage in Atlantis instances.
  3. Define workflows - plan and apply steps, with any extra commands you require.
  4. Set autoplan - choose when plans run automatically on changes to branches.
  5. Add auth notes - token and webhook secret placeholders to fill in later from secrets.
  6. Click Generate configs to build the server and repo files at once.
  7. Review the preview for both server and repo configuration rendered side by side.
  8. Resolve any errors such as a missing project directory entry you forgot.
  9. Copy or download the files for your Atlantis deployment to use and commit.
  10. Wire secrets from your secrets manager before running the server for real.

Examples

Worked example - two projects. Configure GitHub with projects in app/ and data/, each its own workspace, an autoplan on changes, and a workflow that runs terraform fmt and validate before plan. The generator emits a server config pointing at GitHub and an atlantis.yaml declaring both projects with their directories, workspaces and the shared workflow, so a pull request in either directory triggers the right plan and keeps changes isolated per team without any cross-talk between the two.

Benefits

  • Faster setup - skip hand-writing boilerplate YAML files from scratch.
  • Consistent repos - one convention across many projects and teams you manage.
  • Fewer misconfigs - layouts follow Atlantis norms from the very start of the work.
  • Review ready - paste the output into a PR for fast and clear sign-off.
  • Portable - works with any Atlantis host you already run in your estate.
  • Private - nothing is uploaded to a third party during the build step at all.
  • Scalable - repeat the pattern for every repository you own and operate.

Frequently Asked Questions

What does this generate?
An atlantis.yaml (version 3) declaring repos, projects (directories) and a default workflow with init/plan and init/apply steps. Optionally requires approval before apply.
What is Atlantis?
Atlantis is a Terraform automation tool that runs plan/apply from pull requests. Its repo-level config lives in atlantis.yaml.
How are projects defined?
Each directory you list becomes a project with autoplan enabled. You can require approval on apply per project.
Does this connect to Atlantis?
No. It only builds the YAML in your browser.
Can I download it?
Yes. Copy, download or print the config.