Title
j
James Burriss
03/10/2023, 3:36 PMHello,
I have recently added Atlantis to our repo (working great for the most part). We are using projects in the atlantis.yaml repo file to specifically mark directories that we want atlantis to interact with. I have noticed that on a few PRs the below error has been shown even though the PR doesn't contain projects in the atlantis.yaml file or any terraform changes. There is also no locks in atlantis at the time. Has anyone encountered this before? Using version 0.22.3. Thanks 🙂
t
Tyler Allen
03/10/2023, 3:38 PMAre you running parallel?
We use https://github.com/transcend-io/terragrunt-atlantis-config (althought we use terragrunt) which will create dynamic workspaces so multiple plans can happen at the same time
j
James Burriss
03/10/2023, 3:39 PMHi Tyler, not that I'm aware of. I believe that is disabled by default and we don't have it set in the config
p
PePe Amengual
03/10/2023, 4:18 PMmonorepo?
j
James Burriss
03/10/2023, 4:18 PMYes
p
PePe Amengual
03/10/2023, 4:19 PMAtlantis locks the PRs per repo
so if two PRs try to plan you will get that message
do you use workspaces?
j
James Burriss
03/10/2023, 4:21 PMNo only the default one
p
PePe Amengual
03/10/2023, 4:21 PMthen this is going to be a problem for you
you can disable locks globally or you can use workspaces
@RB correct me if I'm wrong but the locks are not per dir, right? (there was a PR somewhere to do this I believe)
🤷♂️ 1
j
James Burriss
03/10/2023, 4:25 PMOkay so it happens because there are two PRs planning at the same time. And even if the PRs don't contain files from the projects set in the atlantis.yaml it will still give the errror?
Hey, @PePe Amengual. Sorry to bother you again, just to confirm I would need to disable locking to fix this for now?
p
PePe Amengual
03/21/2023, 3:48 PMit depends, if you want to plan without lock and apply with lock you can use another feature
look at repo_locking: false
j
James Burriss
03/21/2023, 4:13 PMokay thanks!