Luke Kysow 8b77b95a16 Add checkout-strategy flag.
This flag can be set to either branch (default) or merge. If set to
branch, we will check out the head branch of the pull request (the
source). If set to merge, we will check out the base branch of the pull
request (the destination) and then attempt to perform a git merge of the
pull request branch. This simulates what will happen if the pull request
is merged.

This allows us to perform terraform commands on what the state of the
repo will be *after* the pull request is merged. This is useful if users
are often opening up pull requests from branches that aren't up to date
with master. With the branch strategy, the terraform plan might be
deleting resources that have been created in the master branch but with
the merge strategy, we merge the branch's changes into the master branch
and so don't have this problem.
2019-01-15 15:45:01 -05:00
2019-01-07 16:10:21 -05:00
2019-01-15 15:45:01 -05:00
2018-12-12 14:26:46 -06:00
2019-01-15 15:45:01 -05:00
2019-01-10 17:42:30 -05:00
2018-07-24 17:02:01 +02:00
2018-12-20 13:11:37 -06:00
2018-12-17 17:03:05 -05:00
2018-12-19 10:11:35 -08:00
2019-01-10 17:42:30 -05:00
2018-12-12 12:41:33 -06:00
2018-03-15 17:25:02 -07:00
2018-12-20 13:11:37 -06:00
2018-08-08 16:49:43 -10:00
2018-08-16 13:02:09 -10:00
2018-08-16 13:02:09 -10:00

Atlantis

Atlantis Logo

Terraform For Teams

Resources

What is Atlantis?

A self-hosted golang application that listens for Terraform pull request events via webhooks.

What does it do?

Runs terraform plan and apply remotely and comments back on the pull request with the output.

Why should you use it?

  • Make Terraform changes visible to your whole team.
  • Enable non-operations engineers to collaborate on Terraform.
  • Standardize your Terraform workflows.

Badges!

SuperDopeBadge Go Report Card CircleCI Slack Status Gitter chat

Description
Terraform Pull Request Automation
Readme 215 MiB