From 94a1e59b78887a8b4dd3e1bbe4cc5e60f129f685 Mon Sep 17 00:00:00 2001 From: Jon Gilmore <7232986+JonGilmore@users.noreply.github.com> Date: Sun, 11 Dec 2022 19:31:31 -0600 Subject: [PATCH 1/2] 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. --- runatlantis.io/docs/faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/runatlantis.io/docs/faq.md b/runatlantis.io/docs/faq.md index 379bd74e99..44ef626fdf 100644 --- a/runatlantis.io/docs/faq.md +++ b/runatlantis.io/docs/faq.md @@ -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 you are planning to run multiple Atlantis hosts (utilizing a shared redis backend), you will want to make sure 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. @@ -25,4 +25,4 @@ See `atlantis server --help` for more information. **Q: How can I get Atlantis up and running on AWS?** -A: There is [terraform-aws-atlantis](https://github.com/terraform-aws-modules/terraform-aws-atlantis) project where complete Terraform configurations for running Atlantis on AWS Fargate are hosted. Tested and maintained. \ No newline at end of file +A: There is [terraform-aws-atlantis](https://github.com/terraform-aws-modules/terraform-aws-atlantis) project where complete Terraform configurations for running Atlantis on AWS Fargate are hosted. Tested and maintained. From 97b35f06da3bc7cc7811b7913f646e246afca688 Mon Sep 17 00:00:00 2001 From: Jon Gilmore <7232986+JonGilmore@users.noreply.github.com> Date: Mon, 12 Dec 2022 09:19:20 -0600 Subject: [PATCH 2/2] Update runatlantis.io/docs/faq.md Co-authored-by: nitrocode <7775707+nitrocode@users.noreply.github.com> --- runatlantis.io/docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runatlantis.io/docs/faq.md b/runatlantis.io/docs/faq.md index 44ef626fdf..4465e09f86 100644 --- a/runatlantis.io/docs/faq.md +++ b/runatlantis.io/docs/faq.md @@ -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, by default, stores all locking and Terraform plans locally on disk under the `--data-dir` directory (defaults to `~/.atlantis`). If you are planning to run multiple Atlantis hosts (utilizing a shared redis backend), you will want to make sure that the `data-dir` is using a shared filesystem between hosts. +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.