Bugfix release.
- Fix
required_version
detection not working for Terraform 0.13.0 (#1153 by @joerx) - Fix editing comments on draft PRs causing plan to re-run (#1194)
- Fix Azure DevOps apply status checks not working (#1172 by @acastle)
- Fix checkout-strategy=merge not working when using the GitHub app installation (#1193 by @nishkrishnan)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.13.4. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.15.0...v0.15.1
Relatively small release with some bugfixes and a couple of features. Also sets default Terraform version to 0.13.0.
- Bump default Terraform version to 0.13.0
- Retry GitHub calls to prevent 404 issues (#1019)
- Update GitLab library to handle rate limiting issues (#1142 by @LAKostis)
- Alpine version n Docker image is now 3.12 (up from 3.11) (#1136 by @lazzurs)
- Add new flag
--skip-clone-no-changes
that will skip cloning the repo during autoplan if there are no changes to Terraform projects. This will only apply for GitHub and GitLab and only for repos that haveatlantis.yaml
files. (#1158 by @cucxabong) - Add new flag
--disable-autoplan
that will globally disable autoplanning. (#1159 by @ValdirGuerra)
- Fix
--hide-prev-plan-comments
bug (#1009 by @goodspark) - Fix comment splitting bug (#1109 by @crainte)
- Fix Azure DevOps bug when cloning a repo with spaces in its name (#1079 by @mcdafydd)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.13.0. Simply set the above flag to your desired default version to avoid any issues. --repo-whitelist
is now deprecated in favour of--repo-allowlist
. The previous flag will still work.
https://github.com/runatlantis/atlantis/compare/v0.14.0...v0.15.0
This release brings a big new feature: the ability to install Atlantis as a GitHub App! Thanks to @unRob for this amazing feature.
- Support installation via a GitHub App. See https://www.runatlantis.io/docs/access-credentials.html#github-app for instructions. (#1088 by @unRob)
- Add new
atlantis unlock
command that can be run on pull requests to discard all plans and unlock all projects associated with that PR. (#1091 by @parmouraly) - Add debug-level logging for GitHub calls (#1042 by @cket)
- The repo-relative directory is now available in custom workflows via the environment variable
REPO_REL_DIR
(#1063 by @llamahunter) - Upgrade the default Terraform version to 0.12.27.
- Update jQuery to 1.5.1 to fix a security issue with the older version.
- Update
gosu
in the Atlantis Docker image to 1.12 (#1104 by @lazzurs) - Ignore changes to
.tflint.hcl
(#1075 by @unRob)
--write-git-credentials
now works with Azure DevOps (#1070 by @markbrennan)- Partly fix
--hide-prev-plan-comments
on GitHub Enterprise (#1072 by @goodspark) - Fix bug where Atlantis would auto-merge a PR if
apply
was run after the locks were discarded (Fixes #1006 by @parmouraly) - Fix bug when using
--hide-prev-plan-comments
where if a plan output was split across multiple comments only the first comment would get hidden (Fixes #1021 by @crainte)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.27. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.13.0...v0.14.0
This release enables support for running plans and applies in parallel only when using Terraform workspaces. It also enables graceful shutdown for Atlantis where it waits for in-progress plans and applies to complete. See below for the complete list.
-
Upgrade default Terraform version in Docker image to 0.12.26.
-
Add support for parallel plans and applies (#926 by @Fauzyy)
Running in parallel is only supported if you're using workspaces to separate your projects. Projects in separate directories can not be run in parallel currently. To use, set
parallel_plan: true parallel_apply: true
In your repo-level
atlantis.yaml
file. -
Add support for graceful shutdown (#1051 by @benoit74). When Atlantis receive a SIGINT or SIGTERM it won't shut down immediately. It will wait for in-progress plans and applies to complete. Any new actions, e.g. comments or autoplans will be refused and an error comment will be posted to the PR indicating that Atlantis is shutting down and the user should try again later.
In addition, a new
/status
endpoint has been added that currently only returns the number of in-progress operations and whether the server is shutting down. -
GitHub: A new flag
--allow-draft-prs
has been added that will re-enable the ability for users to run plan and apply on GitHub draft PRs. This ability was removed in v0.12.0. (#1053 by @cket) -
GitHub: Preserve original commit message when automerging (#1049 by @pratikmallya).
This change removes the
[Atlantis] Automatically merging after successful apply
commit message and instead has GitHub autogenerate the commit message similarly to how it would when you click the "Merge" button in the UI. -
Change log level for HTTP requests from INFO to DBUG, e.g.
2020/05/26 12:16:20+0000 [INFO] server: GET /healthz – respond HTTP 200 2020/05/26 12:16:36+0000 [INFO] server: GET /healthz – from <IP>
(#1056 by @tammert)
-
GitLab: Use correct link to merge requests (previously used
#<num>
instead of!<num>
) (#1059 by @EppO)
- Azure DevOps: Project links link to pull requests now (Fixes #957 by @mcdafydd)
- GitHub: Release locks when GitHub draft PRs are closed (#1038 by @andrewring)
- Ensure git-lfs is in our Docker image (Fixes #1054)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.26. Simply set the above flag to your desired default version to avoid any issues. - HTTP requests are now logged as DBUG instead of INFO to reduce log spam. If you
still want to see these logs you must run with
--log-level=debug
. - Atlantis will no longer immediately shutdown when it receives a SIGINT or SIGTERM, it will now wait for in-progress plans and applies to complete. To stop Atlantis without waiting, send a SIGKILL.
https://github.com/runatlantis/atlantis/compare/v0.12.0...v0.13.0
This release contains one much-awaited GitHub-only feature: the ability to hide previous
plan comments with the --hide-prev-plan-comments
flag. It also contains
a host of other small features and fags.
- GitHub: Add
--hide-prev-plan-comments
flag. When set, previous plan comments will be marked as outdated in GitHub's UI. This collapses them making a PR with lots of plan comments easier to read. (#994 by @goodspark) - GitHub: Ignore draft PRs until they're changed to "ready for review". (#977 by @cket)
- Upgrade default Terraform version in Docker image to 0.12.24.
- Set
as_user
param when sending slack notifications so the message is decorated appropriately (#907 by @tmcevoy14) - Add Git LFS support (#872 by @remilapeyre)
- Add
--silence-vcs-status-no-plans
flag that silences VCS commit status when autoplan finds no projects to plan. When set, Atlantis won't create any VCS statuses if there no projects to plan. (#959 by @cket) - Add
--disable-markdown-folding
flag that disables folding for long plan/apply outputs. (#960 by @mhumeSF) - Ignore casing when setting log levels, e.g.
--log-level=INFO
now works. (#976 by @jpreese) - Azure DevOps: Add policy checking. (#984 by @jpreese)
- Upgrade boltdb to latest maintained version. (#992 by @amasover)
- Azure DevOps: Prevent pull request updated events from triggering autoplan when the event was caused by a change in approvals. (Fixes #946 by @mcdafydd)
- GitHub draft PRs are now ignored until they're marked "ready for review" and opened as regular PRs.
**NOTE: ** This functionality was added back in Atlantis v0.13.0 via the
--allow-draft-prs
flag. - If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.24. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.11.1...v0.12.0
Using the latest Alpine Docker image (3.11) to mitigate some vulnerabilities in that image.
- Use Alpine 3.11 to mitigate:
- CVE-2019-5482:
curl <7.66.0-r0
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5482 - CVE-2019-5481:
curl <7.66.0-r0
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5481 - CVE-2019-15903:
expat <2.2.7-r1
andgit <2.22.0r0
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15903 - CVE-2018-20843:
expat <2.2.7-r0
andgit <2.22.0-r0
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20843 - CVE-2019-14697:
musl <1.1.22-r3
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697
- CVE-2019-5482:
https://github.com/runatlantis/atlantis/compare/v0.11.0...v0.11.1
Small release with a couple new config flags from contributors.
- Upgrade default Terraform version in Docker image to 0.12.19.
- Add new
--tf-download-url
flag to allow overriding the default download base URL ofhttps://releases.hashicorp.com
. (#787 by @cullenmcdermott) - Add new
--vcs-status-name
flag to allow configuring the name Atlantis uses for its PR statuses. Useful if running multiple Atlantis servers on the same repo. (#841 by @js-timbirkett) - Add new
--silence-fork-pr-errors
flag to silence errors from fork PRs in orgs that use fork PRs for non-terraform changes. (#885 by @kinghrothgar)
- Fix Atlantis Dockerfile subcommand detection (Fixes #870 by @sparky005)
- Fix
--write-git-creds
command for BitBucket modules (Fixes #873 by @ImperialXT) - Fix issue where Atlantis was failing on Azure DevOps PRs with branch protection (Fixes #880 by @mcdafydd)
- Fix issue where project's set with an absolute dir, e.g.
dir: /a/b/c
would actually use that directory instead of making it relative to the reo root (Fixes #849). - Fix issue where changes to
terragrunt.hcl
files weren't being detected when usingatlantis.yaml
files (Fixes #803 by @JoshiiSinfield)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.19. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.10.2...v0.11.0
Some small features in this release and some bug fixes.
- Exclusions are now supported in
when_modified
config so you can ignore changes in files that you don't want to trigger plan on. - Emojis are now supported in Azure DevOps 🎉.
- Upgrade Terraform in Docker image to 0.12.16.
- Add support for kustomize (#785 by @tobbbles)
- Use emojis in comments for Azure DevOps (#863 by @mcdafydd)
- Allow exclusions to be specified in
when_modified
, e.g.when_modified: ["!this-file.tf"]
(#847 by @leonsodhi-lf) - When using
--checkout-strategy=merge
warn users if the branch they're merging into has been updated (#804 by @MRinalducci)
- Support
/
in branch names for Azure DevOps (Fixes #835 by @mcdafydd) - Fix bug where a server-side workflow with the name "default" wasn't being used (Fixes #860)
- Fix GitLab error due to API updates (Fixes #864)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.16. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.10.1...v0.10.2
Small release that is built using Go 1.13.3 to mitigate a CVE (https://99designs.ca/blog/engineering/request-smuggling/).
- Error out when user has an atlantis.yml file (wrong extension, needs .yaml) (#816 by @mdcurran)
None
If you had an atlantis.yml
file (note the .yml
extension), previously Atlantis ignored it.
Now it will error to warn you that it's not being used.
https://github.com/runatlantis/atlantis/compare/v0.10.0...v0.10.1
Lots of new features in this release: Azure DevOps support, automatic Terraform version detection and private module cloning support. All by community contributors!
- Support for Azure DevOps (719 by @mcdafydd)
- Support detecting Terraform version from
terraform { required_version = "=<version>" }
block (#789 by @kennethtxytqw) - Improve
--write-git-creds
command so that it supports ssh private modules (#799 by @ImperialXT) - Default TF version is now 0.12.12
- Logo is now bigger on locks listing (#783 by @Nuru)
- Fix error when using GitLab with the "Delete source branch" setting (Fixes #760)
- Fix repo whitelist when using wildcard in the middle, ex.
github.com/*-something
(Fixes #692 by @dedamico)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.12. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.9.0...v0.10.0
This release contains a new step for custom workflows called env
. It allows
users to set environment variables statically and dynamically for their workflows:
workflows:
env:
plan:
steps:
- env:
name: STATIC
value: set-statically
- env:
name: DYNAMIC
command: echo set-dynamically
- run: echo $STATIC $DYNAMIC # outputs 'set-statically set-dynamically'
- New
env
step in custom workflows (#751) - New flag
--write-git-creds
helps Atlantis support private module sources. (#711) - Upgrade Terraform to 0.12.7 in our base Docker image.
- Support for Terragrunt > 0.19.0 (#748)
- The directory where Atlantis downloads Terraform binaries is now in the PATH of custom workflows (#678)
dumb-init
andgosu
upgraded in our Docker image (#730)
- The Terraform version specified in
terraform_version
is now downloaded even if there are only custom steps (Fixes #675)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.7. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.8.3...v0.9.0
This release contains an important security fix in addition to some fixes and changes for Terraform Cloud/Enterprise users. It's highly recommended that all Atlantis users upgrade to this release. See the Security section below for more details.
- Additional arguments specified in Atlantis comments, ex.
atlantis plan -- -var=foo=bar
are now escaped before being appended to the relevant Terraform command. (Fixes #697). Previously, a comment likeatlantis plan -- -var=$(touch foo)
would execute thetouch foo
command because the extra arguments weren't being escaped properly. This means anyone with comment access to an Atlantis repo could execute arbitrary code. Because of the severity of this issue, all users should upgrade to this version. - Upgrade to latest version of Alpine Linux in our Docker image to mitigate vulnerabilities found in libssh2. (Fixes #687)
- Upgrade Terraform to 0.12.3 in our base Docker image.
- Additional arguments specified in Atlantis comments, ex.
atlantis plan -- -var=foo=bar
are now available in custom run steps as theCOMMENT_ARGS
environment variable. (Fixes #670) - A new flag
--tfe-hostname
is available for specifying a Terraform Enterprise private installation's hostname when using the remote backend integration. (#706)
- Parse Bitbucket Cloud pull request rejected events properly. (Fixes #676)
- Terraform >= 0.12.0 works with Terraform Cloud/Enterprise remote operations. (Fixes #704)
- If you were previously relying on being able to execute code in the additional
arguments of comments, ex.
atlantis plan -- -var='foo=$(echo $SECRET)'
this is no longer possible. Instead you will need to write a custom workflow with a custom step or the extra_args config. - If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.3. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.8.2...v0.8.3
Small bugfix release for Bitbucket Cloud users running with "require mergeable".
- Update default Terraform version to 0.12.1.
- Include directory in Slack message (#660).
- Atlantis would not allow applies for all Bitbucket Cloud pull requests if running with "require mergeable" even if the pull request was mergeable due to an API change. (Fixes #672)
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12.1. Simply set the above flag to your desired default version to avoid any issues.
https://github.com/runatlantis/atlantis/compare/v0.8.1...v0.8.2
Small bugfix release for Bitbucket Cloud users running with require approval.
None
- Atlantis would panic when checking if pull requests were approved for Bitbucket Cloud due to an API change. (Fixes #652)
None
https://github.com/runatlantis/atlantis/compare/v0.8.0...v0.8.1
This release upgrades the default version of Terraform to 0.12.
If you're running Atlantis with the --default-tf-version
flag set (which
you always should) then this won't affect you at all.
- Upgrade default Terraform version to 0.12
- Add new
--disable-apply-all
flag that disables runningatlantis apply
without any flags. (#645)
None
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-version
flag then the default version of Terraform will now be 0.12. Simply set the above flag to your desired default version of Terraform and 0.12 won't be used.
https://github.com/runatlantis/atlantis/compare/v0.7.2...v0.8.0
Small release containing an important security fix and some bugfixes.
None
- Atlantis would post its Git credentials as pull request comment and in logs if the git clone failed. (Fixes #615)
- Atlantis would comment the same output twice during errors of custom run steps. (Fixes #519)
atlantis testdrive
had unreadable output on solarized terminals. (Fixes #575)
None
https://github.com/runatlantis/atlantis/compare/v0.7.1...v0.7.2
Small bugfix release to fix an issue when using --checkout-strategy=merge
.
PROJECT_NAME
is now available as an environment variable to customrun
steps. (#578)
- Fix deleting unapplied plans when
--checkout-strategy=merge
is used. (Fixes #582)
None
https://github.com/runatlantis/atlantis/compare/v0.7.0...v0.7.1
This release implements Server-Side Repo Config which allows users to write
atlantis.yaml
-style config on the server rather than in individual repos.
The Server Side config also allow Atlantis operators to control what individual
repos can do in their atlantis.yaml
files. Read docs for more details.
- Server-Side Repo Config. Read docs
and use cases for full details. (#47)
- New flag
atlantis server
flag--repo-config
for specifying the repo config file . - New flag
--repo-config-json
for specifying the repo config as a JSON string instead of having to write a config file to disk. - All repos can now create
atlantis.yaml
files to configure their projects, however by default, those files can't create custom workflows or set Apply Requirements.
- New flag
- New version
3
ofatlantis.yaml
fixes a small issue with how we were parsing customrun
steps. Previously we were doing additional parsing which caused some users to have to add extra escaping to their commands. Now this is no longer required. See the Backwards Compatibility section for more details.
- Fix bug where running
atlantis apply
to apply all outstanding plans wouldn't work if you had more than one project defined in the exact same directory and workspace. (Fixes #365)
-
The server-side config changes are fully backwards compatible. The biggest difference is that all repos can now create
atlantis.yaml
files, but without being able to create custom workflows or set apply requirements. This will allow users to configure their projects, workspaces and terraform versions at a repo level without enabling those repos to run custom code or circumvent apply requirements set server-side. -
atlantis.yaml
has a new version3
. If you continue to use version2
, you will experience no changes. If you want to upgrade to version3
, then if you're not using any customrun
steps in your workflows you can upgrade the version number without additional changes.If you are using
run
steps, check our upgrade guide to see if you need to make any changes before upgrading. -
Flags
--require-approval
,--require-mergeable
and--allow-repo-config
are deprecated in favour of creating a server-side repo config file that applies the same configuration. If you runatlantis server
with those flags, a deprecation warning will be printed telling you what server-side config is recommended instead. -
If you have projects configured with the same directory and workspace (which means you're probably using the
-backend-config
flag) and their names contain/
's, then you'll have to re-runatlantis plan
after upgrading if you had any unapplied plans.An example of what config would mean you need to re-plan:
projects: - name: name/with/slashes dir: samedir workflow: a - name: another/with/slashes dir: samedir workflow: b a: plan: steps: - run: rm -rf .terraform - init: extra_args: [-backend-config=staging.backend.tfvars] - plan b: plan: steps: - run: rm -rf .terraform - init: extra_args: [-backend-config=staging.backend.tfvars] - plan
https://github.com/runatlantis/atlantis/compare/v0.6.0...v0.7.0
This release introduces a new flag --default-tf-version=<version>
that allows users
to set the version of Terraform that Atlantis defaults to. Atlantis will automatically
download that version on startup so users don't need to build their own custom
Docker images.
Atlantis will also now automatically download any Terraform version specified in
atlantis.yaml
:
version: 2
projects:
- dir: .
terraform_version: v0.12.0-beta1 # Will be downloaded automatically.
- New flag:
--default-tf-version=<version>
will cause Atlantis to automatically download and use that version of Terraform by default. Atlantis will also automatically download terraform versions specified inatlantis.yaml
via theterraform_version
config key. (#538) - New status check names mean that the Atlantis checks will appear together (at least on GitHub). (#545)
- Upgrade base Docker image to use Alpine 3.9. Alpine 3.9 mitigates CVE-2018-19486. (#541)
None
-
Our Docker image
runatlantis/atlantis
has Terraformv0.11.13
now. If you use the new flag--default-tf-version=<desired version>
then you won't be affected by this change (nor for subsequent version upgrades). -
The Atlantis status checks have been renamed from what they looked like in
v0.5.*
. Previously the names were:plan/atlantis
andapply/atlantis
. Now the names areatlantis/plan
andatlantis/apply
.This change will only affect you if you're requiring those status checks to pass via a setting in your Git host (ex. via GitHub protected branches). If so, you'll need to change your settings to require the new names to pass and un-require the old names.
If you were on a version lower than
v0.5.*
then read the backwards compatibility notes for release0.5.0
.NOTE from the maintainer: I take backwards compatibility seriously and I apologize that the status checks are changing again so soon after the 0.5 release also changed them. I know that if you have many repos and require the checks to pass that it is a large task to change them all again.
In this case, I decided that the tradeoff was worth it because the 0.5 release has only been out for a couple of weeks so hopefully not everyone has upgraded to it. The new check names makes them a lot easier to read (at least on GitHub) because they appear next to each other now due to alphabetical sorting. In this case I felt like it was better to get this change done as soon as possible rather than having this annoying UX issue stay around forever.
https://github.com/runatlantis/atlantis/compare/v0.5.1...v0.6.0
This is a bugfix release to fix a bug where Atlantis was replying to comments that weren't directed to it.
Diff: https://github.com/runatlantis/atlantis/compare/v0.5.0...v0.5.1
- On Bitbucket Cloud and Server, Atlantis now responds if it's invoked with the username it's running under, ex. @my-bb-atlantis-user. This is the same functionality as GitHub and GitLab. (#534)
- Atlantis ignore comments that aren't addressed to it. (Fixes #533)
- On Bitbucket Cloud and Server, Atlantis now responds if it's invoked with the username it's running under, ex. @my-bb-atlantis-user. This is the same functionality as GitHub and GitLab.
This release has two big features: New Status Checks and Terraform Enterprise Integration.
New Status Checks:
The new status checks split the old status check into plan
and apply
phases.
Each check now tracks the status of each project modified in the pull request.
For example if two projects are modified, the plan
check might read:
2/2 projects planned successfully.
And the apply
check might read:
0/2 projects applied successfully.
Users can now use their Git host's settings to require these checks pass before a pull request is merged and be confident that all changes have been applied (for example).
Terraform Enterprise Integration:
Atlantis now integrates with the Terraform Enterprise (TFE)
via the remote backend.
Atlantis will run terraform
commands as usual, however those commands will
actually be executed remotely in Terraform Enterprise.
Using Atlantis with Terraform Enterprise gives you access to TFE features like:
- Real-time streaming output
- Ability to cancel in-progress commands
- Secret variables
- Sentinel Without having to change your pull request workflow.
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.15...v0.5.0
- Split single status check into one for
plan
and one forapply
(see above). - Support using Atlantis with Terraform Enterprise via remote operations (see above).
- Add
USER_NAME
environment variable for custom steps to use. (#489) - Support Bitbucket Cloud's upcoming API deprecations. (#502)
- Support Bitbucket Server hosted at a basepath, ex.
bitbucket.mycompany.com/pathprefix
(Fixes #508)
- Allow Bitbucket Server diagnostics checks. (Fixes #474)
- Fix automerge for Bitbucket Server. (Fixes #479)
- Run
terraform init
with-upgrade
. (Fixes #443) - If a pull request is deleted in Bitbucket Server, delete locks. (Fixes #498)
- Support directories with spaces, ex
atlantis plan -d 'dir with spaces'
. (Fixes #423) - Ignore Terragrunt cache directories that were causing duplicate applies. (Fixes #487)
- Fix
atlantis testdrive
for latest version of ngrok.
-
New Status Checks - If you have settings in your Git host that require the Atlantis commit status check to be in a certain condition, you will need to modify that setting as follows:
Previously, Atlantis set a single check with the name
Atlantis
. Now there are two checks with the namesplan/atlantis
andapply/atlantis
. If you had previously required theAtlantis
check to pass, you should now require both theplan/atlantis
andapply/atlantis
checks to pass.The behaviour has also changed. Previously, the single Atlantis check would represent the status of the last run command. For example, if I ran
atlantis plan
and it failed, the check would be in a Failed state. If I ranatlantis apply -p project1
and it succeeded, then the check would be in a Success state, regardless of the status of other projects in the pull request.Now, each check represents the plan/apply status of all projects modified in the pull request. For example, say I open up a pull request that modifies two projects, one in directory
proj1
and the other inproj2
. If autoplanning is enabled, and both plans succeed, then there will be a single status check:plan/atlantis - 2/2 projects planned successfully
(success)
If I run
atlantis apply -d proj1
, then Atlantis will set a pending apply check:plan/atlantis - 2/2 projects planned successfully
(success)apply/atlantis - 1/2 projects applied successfully
(pending)
If I apply the final project with
atlantis apply -d proj2
, then my checks will look like:plan/atlantis - 2/2 projects planned successfully
(success)apply/atlantis - 2/2 projects applied successfully
(success)
-
terraform init
is now run with-upgrade=true
. Previously, it used Terraform's default setting which wasfalse
.This means that
terraform
will always update to the latest version of plugins and modules. For example, if you're using a module source ofsource = "git::https://example.com/vpc.git?ref=master"
then
terraform init
will now always use the version onmaster
whereas previously, if you had already runatlantis plan
beforemaster
was updated, a newatlantis plan
wouldn't pull the latest changes and would just use the cached version.This is unlikely to cause any issues because most users already expected Atlantis to use the most up-to-date version of modules/plugins within the set constraints.
This is a bugfix release containing an important fix to how Atlantis executes Terraform. A bug was introduced in v0.4.14 that causes Atlantis to hang indefinitely when executing Terraform when there is a lot of output from Terraform.
In addition, there's a fix to automerge when you require rebasing or commit squashing in GitHub and a fix for the mergeability check if you're requiring the Atlantis status to pass in GitHub.
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.14...v0.4.15
None – this is a bugfix release.
- Atlantis hangs on large plans. (Fixes #474)
- Automerge now works on GitHub if you require a rebase or squash merge. (#466)
- Automerge now works on Bitbucket if previously you were getting XSRF errors. (Fixes #465)
- Requiring
mergeable
now works on GitHub if you are also requiring the Atlantis status to pass before merging. (Fixes #453)
None
WARNING: This release contains a bug that causes Terraform execution to stall on large infrastructures. Please use v0.4.15 instead.
This release contains two big new features: Automerge and Checkout Strategy.
Automerge is a much asked for feature that allows Atlantis to automatically
merge your pull requests if all plans have been applied successfully.
It can be enabled via the --automerge
flag, or via an atlantis.yaml
setting:
version: 2
automerge: true
projects:
- ...
Checkout Strategy allows you to choose if Atlantis checks out the exact branch
from the pull request or what the destination branch will look like once the pull
request is merged. You can choose your checkout strategy via the --checkout-strategy
flag which supports branch
(the default) or merge
.
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.13...v0.4.14
- Can now be configured to automatically merge pull requests after all plans have been applied. See https://www.runatlantis.io/docs/automerging.html. (Fixes #186)
- New
--checkout-strategy
flag which supports checking out the code as it will look once the pull request was merged. Previously we only supported checking out the pull request branch which might be out of date with the destination branch and so cause Terraform to delete resources that have already been applied. See https://www.runatlantis.io/docs/checkout-strategy.html. (Fixes #35 - Support Terraform 0.12 by version detection and then changing how Atlantis runs its Terraform commands. (#419)
- New
--tfe-token
flag to support using Terraform Enterprise's Free Remote State Storage. (#419)
- Run plan in directory when file is moved. (Fixes #413)
- Fix bug where when Terraform crashed, Atlantis would hang indefinitely. (#421)
None
The release downloads have been deleted because this release contains a critical bug
The release downloads have been deleted because this release contains a critical bug
This release is focused on quick-wins, bugfixes and one new feature that allows
users to require pull requests be "mergeable", before allowing for atlantis apply
.
The mergeable apply requirement is very useful for GitHub users where it allows them to require pull requests be approved by specific users or require certain status checks to pass. See https://www.runatlantis.io/docs/apply-requirements.html#mergeable for more information.
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.12...v0.4.13
-
Introduce a new (optional)
mergeable
apply requirement that requires pull requests to be mergeable prior to allowingapply
to run. (Fixes #43) -
If users have workspaces configured for a directory via an
atlantis.yaml
file, only allow commands to be run on those workspaces. All commands attempted to be run on different workspaces will error out.For example, if I have an
atlantis.yaml
file:version: 2 projects: - dir: mydir workspace: default - dir: mydir workspace: staging
Then I can run
atlantis apply -d mydir -w default
andatlantis apply -d mydir -w staging
but I will receive an error if I runatlantis apply -d mydir -w somethingelse
. -
If users are setting the
name
key for their projects inatlantis.yaml
, then include the project name in the comment output so it's easier to identify which plan/apply output is for which project. (Fixes #353)) -
Bump the Terraform version in the Docker image to
0.11.11
. -
Tweak logging to add timezone to the timestamp and make the output more readable. (#402)
-
Warn users if running
atlantis apply -- -target=myresource
because-target
can only be specified duringatlantis plan
. (Fixes #399)
- If
terraform plan
returns an error, print the error to the pull request. (#381) - Split Bitbucket Server comments into multiple comments if over the max size. (Fixes #280)
- Fix issue where if users specified
--gitlab-hostname
without a scheme then Atlantis wouldn't parse the URL correctly. (#377) - Give better error message if GitLab users are commenting on commits instead of a merge request. (Fixes #150, #390)
- If an error occurs early in request processing, comment that error back on the pull request. Previously, we were commenting back on errors but not for errors very early in the processing. (Fixes #398)
-
The version of Terraform installed in the
runatlantis/atlantis
Docker image is now0.11.11
. Previously it was0.11.10
. -
If you are a) using an
atlantis.yaml
file and b) defining Terraform workspaces and c) running plan and apply against workspaces that were not defined in theatlantis.yaml
file, then this no longer works.You will now need to define all the workspaces in the
atlantis.yaml
file. For example, say you had the following config:version: 2 projects: - dir: mydir workspace: production
And you used to run:
atlantis plan -d mydir -w anotherworkspace atlantis apply -d mydir -w anotherworkspace
For this to work now, you need to add the
anotherworkspace
workspace to youratlantis.yaml
file:version: 2 projects: - dir: mydir workspace: production - dir: mydir workspace: anotherworkspace
Small feature and bug fix release. If you're using GitLab <11.1 then your comment formatting is fixed!
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.11...v0.4.12
- Atlantis can now be hosted behind a path-based router and its UI will still
render correctly. For example, you could host atlantis at mydomain.com/mypath,
then run
atlantis server --atlantis-url https://mydomain.com/mypath
and when atlantis renders its UI, all the URLs will have the/mypath
prefix so the UI renders properly. (Fixes #213) - Log warning if GitLab hostname isn't resolvable. (Fixes #359)
- Support running our official Docker image
runatlantis/atlantis
on OpenShift. OpenShift runs images with random uids so we needed to build in support for that. (Fixes #345)
- If the output is too long for a single GitHub comment, maintain formatting when splitting into multiple comments. (Fixes #111)
- Fix bug with using the pagination API in BitBucket. (#354)
- If using GitLab < 11.1 then don't use expandable markdown comments. (Fixes #315)
- Fix output from custom steps that came before the plan step from being removed. (#367)
We made changes to the base image (runatlantis/atlantis-base
) that
runatlantis/atlantis
is built off of. These changes should not affect your
running of atlantis unless you're building your own custom images and were relying
on specific user permissions. Even then we don't anticipate any problems.
These are the changes in detail:
-
Previously, the permissions of
/home/atlantis
were:$ ls -la /home/atlantis/ drwxr-sr-x 2 atlantis atlantis 4096 Sep 13 22:49 .
Now they are:
$ ls -la /home/atlantis/ drwxrwxr-x 2 atlantis root 4096 Nov 28 21:22 .
- The directory is now owned by the
root
group. - Its group permissions now include
w
andx
.
This was needed because OpenShift runs Docker images as random uid's under the root group and so now those random uid's can use
/home/atlantis
as their data directory. - The directory is now owned by the
-
Previously, the
atlantis
user was only part of its own group:$ gosu atlantis sh $ whoami atlantis $ groups atlantis
Now it's also part of the
root
group:$ gosu atlantis sh $ groups atlantis root
-
Previously, the permissions for
/etc/passwd
were:$ ls -la /etc/passwd -rw-r--r-- 1 root root 1284 Sep 13 22:49 /etc/passwd
Now the permissions are:
$ ls -la /etc/passwd -rw-rw-r-- 1 root root 1284 Nov 28 21:22 /etc/passwd
The
w
group permission was added so that in OpenShift, the random uid can write their own login entry (https://github.com/runatlantis/atlantis/blob/master/docker-entrypoint.sh#L28) which is required becauseterraform
expects the running user to have an entry in/etc/passwd
.
Medium sized release that updates the Terraform version and makes terraform plan
output smaller by removing the Refreshing...
output.
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.10...v0.4.11
- Upgraded Docker image to use Terraform 0.11.10
terraform plan
output is shorter now thanks to remove theRefreshing...
output (#339)- Project names specified in
atlantis.yaml
can now contain/
's. This is useful if you want to name your projects similar to the directories they're in. (Fixes #253) - Added new flag
--silence-whitelist-errors
which prevents Atlantis from comment back on pull requests from non-whitelisted repos. This is useful if you want to add the Atlantis webhook to a whole organization and then control which repos are actioned on via the whitelist. (Fixes #312) - The message when the project is locked is now more helpful. (#336)
- Run
terraform plan
with-var atlantis_repo_owner=runatlantis -var atlantis_repo_name=atlantis -var atlantis_pull_num=10
(if the repo was runatlantis/atlantis) (#300)
- Quote plan filenames so that Bitbucket projects with spaces in their names still work (Fixes #302)
-
Atlantis now runs
terraform plan
with-var atlantis_repo_owner=runatlantis \ -var atlantis_repo_name=atlantis \ -var atlantis_pull_num=10
(in this example the repo that Atlantis is running on is runatlantis/atlantis).
If you were using those variables in your terraform code:
variable "atlantis_repo_owner" { default = "my_default" }
Then Atlantis will be overriding those variables with its own values. To prevent this, you need to rename your variables.
If you aren't using those variables then this change won't affect you.
Small bugfix release to fix issues with new comment format.
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.9...v0.4.10
None
- Fix bad comment rendering (#294)
- Fix
plan
not working on Bitbucket Server when repo owner contains spaces (#290)
None
This release is mostly focused on changing how comments look. Terraform output is now automatically hidden if it's over 12 lines long: Also the red and green highlighting for added and removed resources is fixed:
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.8...v0.4.9
- Terraform output over 12 lines is hidden in comment until expanded
terraform plan
output is highlighted correctly- Terraform is now executed with
-var atlantis_repo={repo name} -var atlantis_pull_num {pull num}
. This will allow users to trace Atlantisterraform
executions in CloudTrail back to a specific user and pull request if using assume role by creating a specific name for the session Terraform initiates.
provider "aws" {
assume_role {
role_arn = "arn:aws:iam::ACCOUNT_ID:role/ROLE_NAME"
session_name = "${var.atlantis_user}-${var.atlantis_repo}-${var.atlantis_pull_num}"
}
}
- Run terraform with
-input=false
(#268).
- We set two new Terraform variables:
atlantis_repo
andatlantis_pull_num
. If you were using variables with those names in your code you will need to rename them in your code.
Security release to upgrade the Docker image to the latest version of Alpine linux that fixes this bug: https://justi.cz/security/2018/09/13/alpine-apk-rce.html
Diff: https://github.com/runatlantis/atlantis/compare/v0.4.7...v0.4.8
None
- Change server startup message to INFO from WARN level.
None
Support GitLab repos nested under multiple levels and use the latest version of Terraform: 0.11.8!
- Support GitLab groups which allow repos to be nested under multiple levels,
ex.
gitlab.com/owner/group/subgroup/subsubgroup/repo
- Use latest version of Terraform: 0.11.8 in Docker image
- When running with
TF_LOG
set, Atlantis will start normally. Previously it would error out due to attempting to parse the stderr output of theterraform version
command.
None
Just a small bugfix release.
None
- If
terraform init
fails, include the failure logs in the comment posted back to the PR.
None
atlantis apply
now applies all unapplied plans instead of just the plan in the root directory. (#169)atlantis plan
now plans all modified projects instead of just the root directory.- Plan comments now contain instructions for how to run apply or re-run plan.
- Ignore approvals from the pull request author (Bitbucket Cloud only). Fixes (#201)
- When double clicking on a GitHub comment, ex.
GitHub would add two newlines to the end. If this was then pasted into a new comment, Atlantis would accept it because of the extra newlines. This has been fixed and the comment with two newlines will be accepted.
atlantis apply
atlantis apply
now applies all unapplied plans. Previously it would only apply the plan in the root directory and default workspace.atlantis plan
now plans all modified projects. Previously it would only run plan in the root directory and default workspace.
- Supports Bitbucket Server (#190).
- Fix
/etc/hosts
not being respected (#196).
None
- Supports Bitbucket Cloud (bitbucket.org) (#30).
None
None
- Don't comment on pull request if autoplan determines there are no projects to plan in. This was getting very noisy for users who use their repos for more than just Terraform (#183).
None
None
- Add new
/healthz
endpoint for health checking in Kubernetes (#102) - Set
$PLANFILE
environment variable to expected location of plan file when running custom steps (#168)- This enables overriding the command Atlantis uses to
plan
and substituting your own or piping through a custom script.
- This enables overriding the command Atlantis uses to
- Changed default pattern to detect changed files to
*.tf*
from*.tf
in order to trigger on.tfvars
files.
None
None
- Autoplanning - Atlantis will automatically run
plan
on new pull requests and when new commits are pushed to the pull request. - New repository
atlantis.yaml
format that supports:- Complete customization of plans run
- Single config file for whole repository
- Controlling autoplanning
- Moved docs to standalone website from the README.
- Fixes:
- The old
atlantis.yaml
config file format is not supported. You will need to migrate to the new config format, see: https://www.runatlantis.io/docs/upgrading-atlantis-yaml.html - To use the new config file, you must run Atlantis with
--allow-repo-config
. - Atlantis will now try to automatically plan. To disable this, you'll need to create an
atlantis.yaml
file as follows:
version: 2
projects:
- dir: mydir
autoplan:
enabled: false
atlantis apply
no longer applies all un-applied plans but instead applies only the plan in the root directory and default workspace. This will be reverted in an upcoming releaseatlantis plan
no longer plans in all modified projects but instead runs plan only in the root directory and default workspace. This will be reverted in an upcoming release.
None
- If the
TF_LOG
environment variable is set, should still be able to start. Previouslyatlantis server
would exit immediately because it couldn't parse the output ofterraform version
.
None
- Rename
atlantis bootstrap
toatlantis testdrive
to make it clearer that it doesn't set up Atlantis for you. Fixes (#129). - Atlantis will now comment on a pull request when a plan/lock is discarded from the Atlantis UI. Fixes (#27).
- Fix issue during
atlantis bootstrap
where ngrok tunnel took a long time to start. Atlantis will now wait until it sees the expected log entry before continuing. Fixes (#92). - Fix missing error checking during
atlantis bootstrap
. (#130).
atlantis bootstrap
renamed toatlantis testdrive
- None
- Fix GitLab approvals not actually checking approval (#114)
- None
- Terraform 0.11.7 in Docker image
- Docker build now verifies terraform install via checksum
- None
- None
--repo-whitelist
is now case insensitive. Fixes (#95).
- None
atlantis server -h
has newlines between flags so it's easier to read (#91).
atlantis bootstrap
uses a custom ngrok config file so it should work even if the user is already running another ngrok tunnel (#93).
- None
- Log a warning if unable to update commit status. (#84)
- None
This release delivers some speed improvements through caching plugins and
not running terraform workspace select
unnecessarily. In my testing it saves ~20s per run.
- All config flags can now be specified by environment variables. Fixes (#38).
- Completed thanks to @psalaberria002!
- Run terraform with the
TF_PLUGIN_CACHE_DIR
env var set. Fixes (#34).- This will cache plugins and make
terraform init
faster. Terraform will still download new versions of plugins. See https://www.terraform.io/docs/configuration/providers.html#provider-plugin-cache for more details. - In my testing this saves >10s per run.
- This will cache plugins and make
- Run terraform with
TF_IN_AUTOMATION=true
so the output won't contain suggestions to run commands that you can't run via Atlantis. (#82). - Don't run
terraform workspace select
unless we actually need to switch workspaces. (#82).- In my testing this saves ~10s.
- Validate that workspace doesn't contain a path when running ex.
atlantis plan -w /jdlkj
. This was already not a valid workspace name according to Terraform. (#78). - Error out if
ngrok
is already running when runningatlantis bootstrap
(#81).
- None
- Atlantis version shown in footer of web UI. Fixes (#33).
- GitHub comments greater than the max length will be split into multiple comments. Fixes (#55).
- None
This release focused on some security issues reported by @eriksw, thanks Erik! By default, Atlantis will be more secure now and you'll have to specify which repositories you want it to work on.
- New flag
--allow-fork-prs
added toatlantis server
controls whether Atlantis will operate on pull requests from forks. Defaults tofalse
. This flag was added because on a public repository anyone could open up a pull request to your repo and use your Atlantis install. - New mandatory flag
--repo-whitelist
added toatlantis server
controls which repos Atlantis will operate on. This flag was added so that if a webhook secret is compromised (or you're not using webhook secrets) Atlantis won't be used on repos you don't control. - Warn if running
atlantis server
without any webhook secrets set. This is dangerous because without a webhook secret, an attacker could spoof requests to Atlantis. - Make CLI output more readable by setting a fixed column width.
- None
- Must set
--allow-fork-prs
now if you want to run Atlantis on pull requests from forked repos. - Must set
--repo-whitelist
in order to startatlantis server
. Seeatlantis server --help
for how that flag works.
- None
- Run apply in correct directory when using
-d
flag. Fixes (#22)
- None
- Fix security issue where Atlantis wasn't escaping the optional "extra args" that could be appended to comments (#16)
- example exploit:
atlantis plan ; cat /etc/passwd
- example exploit:
- Atlantis moved to new repo:
atlantisrun/atlantis
. Read why here - New -w/--workspace and -d/--dir flags in comments (#14)
- You can now specify which directory to plan/apply in, ex.
atlantis plan -d dir1/dir2
- You can now specify which directory to plan/apply in, ex.
- Better feedback from atlantis when asking for help via comments, ex.
atlantis plan -h
- Convert
--data-dir
paths to absolute from relative. Fixes (#245) - Don't run plan in the parent of
modules/
unless there's amain.tf
present. Fixes (#12)
- You must use the
-w
flag to specify a workspace when commenting now- Previously:
atlantis plan staging
, now:atlantis plan -w staging
- Previously:
- You must use a double-dash between Atlantis flags and extra args to be appended to the terraform command
- Previously:
atlantis plan -target=resource
, now:atlantis plan -- -target=resource
- Previously:
- Atlantis will no longer run
plan
in the parent directory ofmodules/
unless there is amain.tf
in that directory.
- SSL support added (#233)
- GitLab custom URL for GitLab Enterprise installations now works (#231)
None
None
- Use
env
instead ofworkspace
for Terraform 0.9.*
None
None
- The environment variables available when executing commands have changed:
WORKSPACE
=>DIR
- this is the absolute path to the project directory on diskENVIRONMENT
=>WORKSPACE
- this is the name of the Terraform workspace that we're running in (ex. default)
- The schema for storing locks changed. Any old locks will still be held but you will be unable to discard them in the UI.
To fix this, either merge all the open pull requests before upgrading OR delete the
~/.atlantis/atlantis.db
file. This is safe to do because you'll just need to re-runplan
to get your plan back.
- Don't ignore changes in
modules
directories anymore. (#211)
- Don't set
as_user
to true for Slack webhooks so we can integrate as a workspace app. (#206)
None
None
None
- Environment variables are passed through to
extra_arguments
. (#150) - Tested hundreds of lines of code. Test coverage now at 60%. (https://codecov.io/gh/hootsuite/atlantis)
- Modules in list of changed files weren't being filtered. (#193)
- Nil pointer error in bootstrap mode. (#181)
None
- all flags passed to
atlantis plan
oratlantis apply
will now be passed through toterraform
. (#131)
- Fix command parsing when comment ends with newline. (#131)
- Plan and Apply outputs are shown in new line. (#132)
--aws-assume-role-arn
and--aws-region
flags removed. Instead, to name the assume role session with the GitHub username of the user running the Atlantis command use theatlantis_user
terraform variable alongside Terraform's built-in support for assume role (see https://github.com/runatlantis/atlantis/blob/master/README.md#assume-role-session-names)- Atlantis has a docker image now (#123). Here is how you can try it out:
docker run runatlantis/atlantis:v0.1.1 server --gh-user=GITHUB_USERNAME --gh-token=GITHUB_TOKEN