does anyone know (or have ideas) how to fix atlantis (using the upstream fargate module) taking a long time when a lot of PRs are being executed from different repositories
like how to debug on the server, or how to redeploy?
at present we have quite a few PRs currently being planned/applied across a number of repos
when this happens we find that Atlantis slows down massively
not sure if increasing https://github.com/terraform-aws-modules/terraform-aws-atlantis/blob/master/variables.tf#L284-L288 would help?
Nope, don’t do that.
Atlantis uses a local BoltDB, more tasks isn’t what you want.
i thought that might be the case
Terraform configurations for running Atlantis on AWS Fargate. Github, Gitlab and BitBucket are supported - terraform-aws-modules/terraform-aws-atlantis
Beef up the Fargate task size CPU/mem
Makes a big difference
yeh makes sense
ecs_task_memory = 4096 ecs_task_cpu = 2048
Depends how many concurrent plan/apply you expect to run, how long is a piece of string
We also set
ATLANTIS_PARALLEL_POOL_SIZE to 50
what does that do?
I run on a m5.2xlarge (8 vCPU, 32gb mem) EC2 instance and often have hundreds of plans run in parallel.
i thought that only works when using workspaces?
There is a difference I believe between Atlantis workspaces and Terraform workspaces, if that is what you are thinking of
changes applied, lets see what this does to the speed, fingers crossed
If there is a repo level
atlantis.yaml file containing directories
dir2 and a PR comes in that affects the terraform module
dir3, atlantis will show a
0 / 0 approval check for the PR. This seems like a bug, no ?
The repo level atlantis.yaml for dir1 and dir2 version: 3 projects: - dir: dir1 - dir: dir2 A PR for only dir3 and I see this atlantis/apply — 0/0 projects applied successfully. atlantis/plan — 0/0…
and if you run atlantis plan manually it says no plans?
it says no plans
oh, not sure how to run atlantis manually. ill have to check that