Hello, I was reading through these docs and this section seemed incorrect. I assume the 2 commands it supports are atlantis plan/apply and not the underlying 3 terraform commands. Let me know if I'm misinterpreting this. Thanks!
Co-authored-by: Rui Chen <rui@chenrui.dev>
* Delete previous plans on autoplan or atlantis plan
When using non-default workspaces, plans are stored
in pr-and-workspace-specific directories.
If a PR is subsequently updated it might happen that
some of the plans are no longer relevant with regards
to the latest changes.
This change ensures that plans are always deleted
when a generic plan is triggered either by autoplan
or by a "atlantis plan" command.
NB Plans are not cleaned up when specific projects are
planned explicitly with "atlantis plan -p/-d/-w".
* Use DeleteLockCommand to delete locks and workdirs
containing previous plans
Co-authored-by: giuli007 <giuglioz@gmail.com>
* fix: add path to DefaultWorkingDirLocker.TryLock()
In the release notes for v0.13.0: https://github.com/runatlantis/atlantis/blob/master/CHANGELOG.md#features-4
> 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.
This commit adds `path` as an argument to `DefaultWorkingDirLocker.TryLock()` and includes `path` in the `workspaceKey` used to check if a project is locked. This should allow projects in separate directories to run in parallel.
To my knowledge, there is no functional reason that projects in separate directories cannot run in parallel.
All calls to `DefaultWorkingDirLocker.TryLock()` have been updated. A new unit test `TestTryLockWithDifferentPaths` has been added to test the behavior of locking two separate directories with the same workspace name.
* Add documntation for parallel_plan and parallel_apply options
Co-authored-by: Kevin Snyder <kevinsnyder@ip-192-168-4-61.ec2.internal>
Co-authored-by: Kevin Snyder <kevinsnyder@ip-10-60-10-94.ec2.internal>
* Moving logs tab from top navigation bar to docs
* fixing link error
* Update runatlantis.io/.vuepress/config.js
Co-authored-by: Nish Krishnan <nishkrishnan@users.noreply.github.com>
* Add clarity + further policy_check examples to docs
* Fix broken link to Atlantis on AWS Fargate Terraform module
Co-authored-by: Dave Heward <74298782+davidh-unmind@users.noreply.github.com>
* adds AllowedRegexpPrefixes config and use it on the FindProjectsByName method
* adds tests for the new AllowedRegexpPrefixes config
* update documentation with the new AllowedRegexpPrefixes config
* Clarify maximum version limit
When latest Docker image still had terraform 1.0.0, for example, any method of specifying a higher version failed to build. This note clarifies the dependency.
* update the docker image reference
Co-authored-by: rui <rui@chenrui.dev>
Fixes#1695
The branch matcher feature has been implemented in #1383 and #1768.
There is only an example for it, but not in the reference.
https://github.com/runatlantis/atlantis/pull/1383/files#diff-5dd8dd3b7c37191b78109efaaa1bb73184ff7a1690632d687fed7cd748847f5eR31-R34
Add missing the `branch` key in the reference for server side repo config.
I also add a warning for `mergeable` requirement to check the `branch`
setting because I think a typical branch protection rule only restricts
a default branch. We should let users know that someone can potentially
bypass it without the `branch` restriction in atlantis.
`The Silence VCS Status` feature has been implemented in #954. However there is no reference to it in the server side repo config.
Add missing `The Silence VCS Status` `--silence-vcs-status-no-plans` in the reference for server side repo config.
The instructions incorrectly asked to visit "Settings->Integrations" , whereas the correct instruction is to visit "Settings->Webhooks".
This PR fixes the error.
* allow user to pass gh-app-key directly instead of filename
* start fixing tests
* fix make test
* update website with info about new flag
* Apply suggestions from code review
Co-authored-by: Roberto Hidalgo <un@rob.mx>
Co-authored-by: Roberto Hidalgo <un@rob.mx>
