public/atlantis
1
0
Fork 0
mirror of https://git.vectorsigma.ru/public/atlantis.git synced 2026-07-28 22:28:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(ha): wording update when using redis (#2771)

Browse Source 
* docs(ha): wording update when using redis

Because it is now possible to use redis as a backend locking DB for Atlantis, this FAQ should be updated.

* Update runatlantis.io/docs/faq.md

Co-authored-by: nitrocode <7775707+nitrocode@users.noreply.github.com>

Co-authored-by: nitrocode <7775707+nitrocode@users.noreply.github.com>
This commit is contained in:
Jon Gilmore
2022-12-12 09:23:20 -06:00
committed by GitHub
parent a56258435b
commit f974fb5113
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
runatlantis.io/docs/faq.md
View File

@@ -13,7 +13,7 @@ Terraform locking can be used alongside Atlantis locking since Atlantis is simpl
A: Atlantis server can easily be run under the supervision of a init system like `upstart` or `systemd` to make sure `atlantis server` is always running.
Atlantis currently stores all locking and Terraform plans locally on disk under the `--data-dir` directory (defaults to `~/.atlantis`). Because of this there is currently no way to run two or more Atlantis instances concurrently.
Atlantis, by default, stores all locking and Terraform plans locally on disk under the `--data-dir` directory (defaults to `~/.atlantis`). If multiple Atlantis hosts are run by utilizing a shared redis backend, then it's important that the `data-dir` is using a shared filesystem between hosts.
However, if you were to lose the data, all you would need to do is run `atlantis plan` again on the pull requests that are open. If someone tries to run `atlantis apply` after the data has been lost then they will get an error back, so they will have to re-plan anyway.