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=barare now escaped before being appended to the relevant Terraform command. (Fixes #697). Previously, a comment likeatlantis plan -- -var=$(touch foo)would execute thetouch foocommand 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=barare now available in custom run steps as theCOMMENT_ARGSenvironment variable. (Fixes #670) - A new flag
--tfe-hostnameis 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-versionflag 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-versionflag 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-allflag that disables runningatlantis applywithout any flags. (#645)
None
- If you're using the Atlantis Docker image and aren't setting the
--default-tf-versionflag 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 testdrivehad 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_NAMEis now available as an environment variable to customrunsteps. (#578)
- Fix deleting unapplied plans when
--checkout-strategy=mergeis 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 serverflag--repo-configfor specifying the repo config file . - New flag
--repo-config-jsonfor specifying the repo config as a JSON string instead of having to write a config file to disk. - All repos can now create
atlantis.yamlfiles to configure their projects, however by default, those files can't create custom workflows or set Apply Requirements.
- New flag
- New version
3ofatlantis.yamlfixes a small issue with how we were parsing customrunsteps. 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 applyto 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.yamlfiles, 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.yamlhas 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 customrunsteps in your workflows you can upgrade the version number without additional changes.If you are using
runsteps, check our upgrade guide to see if you need to make any changes before upgrading. -
Flags
--require-approval,--require-mergeableand--allow-repo-configare deprecated in favour of creating a server-side repo config file that applies the same configuration. If you runatlantis serverwith 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-configflag) and their names contain/'s, then you'll have to re-runatlantis planafter 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.yamlvia theterraform_versionconfig 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/atlantishas Terraformv0.11.13now. 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/atlantisandapply/atlantis. Now the names areatlantis/planandatlantis/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 compatiblity 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
planand one forapply(see above). - Support using Atlantis with Terraform Enterprise via remote operations (see above).
- Add
USER_NAMEenvironment 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 initwith-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 testdrivefor 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/atlantisandapply/atlantis. If you had previously required theAtlantischeck to pass, you should now require both theplan/atlantisandapply/atlantischecks 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 planand it failed, the check would be in a Failed state. If I ranatlantis apply -p project1and 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
proj1and 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 initis now run with-upgrade=true. Previously, it used Terraform's default setting which wasfalse.This means that
terraformwill 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 initwill now always use the version onmasterwhereas previously, if you had already runatlantis planbeforemasterwas updated, a newatlantis planwouldn'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
mergeablenow 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-strategyflag 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-tokenflag 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)
mergeableapply requirement that requires pull requests to be mergeable prior to allowingapplyto run. (Fixes #43) -
If users have workspaces configured for a directory via an
atlantis.yamlfile, 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.yamlfile:version: 2 projects: - dir: mydir workspace: default - dir: mydir workspace: staging
Then I can run
atlantis apply -d mydir -w defaultandatlantis apply -d mydir -w stagingbut I will receive an error if I runatlantis apply -d mydir -w somethingelse. -
If users are setting the
namekey 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=myresourcebecause-targetcan only be specified duringatlantis plan. (Fixes #399)
- If
terraform planreturns 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-hostnamewithout 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/atlantisDocker image is now0.11.11. Previously it was0.11.10. -
If you are a) using an
atlantis.yamlfile and b) defining Terraform workspaces and c) running plan and apply against workspaces that were not defined in theatlantis.yamlfile, then this no longer works.You will now need to define all the workspaces in the
atlantis.yamlfile. 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 anotherworkspaceFor this to work now, you need to add the
anotherworkspaceworkspace to youratlantis.yamlfile: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/mypathand when atlantis renders its UI, all the URLs will have the/mypathprefix so the UI renders properly. (Fixes #213) - Log warning if GitLab hostname isn't resolvable. (Fixes #359)
- Support running our official Docker image
runatlantis/atlantison 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/atlantiswere:$ 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
rootgroup. - Its group permissions now include
wandx.
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/atlantisas their data directory. - The directory is now owned by the
-
Previously, the
atlantisuser was only part of its own group:$ gosu atlantis sh $ whoami atlantis $ groups atlantis
Now it's also part of the
rootgroup:$ gosu atlantis sh $ groups atlantis root
-
Previously, the permissions for
/etc/passwdwere:$ 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
wgroup 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 becauseterraformexpects 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 planoutput is shorter now thanks to remove theRefreshing...output (#339)- Project names specified in
atlantis.yamlcan 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-errorswhich 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 planwith-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 planwith-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
plannot 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 planoutput 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 Atlantisterraformexecutions 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_repoandatlantis_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_LOGset, Atlantis will start normally. Previously it would error out due to attempting to parse the stderr output of theterraform versioncommand.
None
Just a small bugfix release.
None
- If
terraform initfails, include the failure logs in the comment posted back to the PR.
None
atlantis applynow applies all unapplied plans instead of just the plan in the root directory. (#169)atlantis plannow 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 applynow applies all unapplied plans. Previously it would only apply the plan in the root directory and default workspace.atlantis plannow plans all modified projects. Previously it would only run plan in the root directory and default workspace.
- Supports Bitbucket Server (#190).
- Fix
/etc/hostsnot 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
/healthzendpoint for health checking in Kubernetes (#102) - Set
$PLANFILEenvironment variable to expected location of plan file when running custom steps (#168)- This enables overriding the command Atlantis uses to
planand 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*.tfin order to trigger on.tfvarsfiles.
None
None
- Autoplanning - Atlantis will automatically run
planon new pull requests and when new commits are pushed to the pull request. - New repository
atlantis.yamlformat 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.yamlconfig 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.yamlfile as follows:
version: 2
projects:
- dir: mydir
autoplan:
enabled: falseatlantis applyno 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 planno 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_LOGenvironment variable is set, should still be able to start. Previouslyatlantis serverwould exit immediately because it couldn't parse the output ofterraform version.
None
- Rename
atlantis bootstraptoatlantis testdriveto 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 bootstrapwhere 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 bootstraprenamed 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-whitelistis now case insensitive. Fixes (#95).
- None
atlantis server -hhas newlines between flags so it's easier to read (#91).
atlantis bootstrapuses 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_DIRenv var set. Fixes (#34).- This will cache plugins and make
terraform initfaster. 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=trueso the output won't contain suggestions to run commands that you can't run via Atlantis. (#82). - Don't run
terraform workspace selectunless 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
ngrokis 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-prsadded toatlantis servercontrols 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-whitelistadded toatlantis servercontrols 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 serverwithout 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-prsnow if you want to run Atlantis on pull requests from forked repos. - Must set
--repo-whitelistin order to startatlantis server. Seeatlantis server --helpfor how that flag works.
- None
- Run apply in correct directory when using
-dflag. 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-dirpaths to absolute from relative. Fixes (#245) - Don't run plan in the parent of
modules/unless there's amain.tfpresent. Fixes (#12)
- You must use the
-wflag 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
planin the parent directory ofmodules/unless there is amain.tfin that directory.
- SSL support added (#233)
- GitLab custom URL for GitLab Enterprise installations now works (#231)
None
None
- Use
envinstead ofworkspacefor 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.dbfile. This is safe to do because you'll just need to re-runplanto get your plan back.
- Don't ignore changes in
modulesdirectories anymore. (#211)
- Don't set
as_userto 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 planoratlantis applywill 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-arnand--aws-regionflags removed. Instead, to name the assume role session with the GitHub username of the user running the Atlantis command use theatlantis_userterraform 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