This message was deleted.

I had the same issue on the previous version, and had to configure --disable-autoplan explicitly to prevent this. Looked like atlantis was still checking if it had something to do on commits to PRs.

thanks. So far, I only saw it happen once, so doesn’t seem to happen all the time. Not sure if it had to do with the files changed in that specific PR, the restart of Atlantis itself, or something else

@Dylan Page is this related locks or the pot_workflows? do you remember?

@PePe Amengual @Gabriel Martinez @wby Yes this is related to the problem discussed in the ADR-002 doc. Especially with Pre/Post Workflow hooks. The hooks clone and take out a file lock and can cause the clash. The details are in the ADR

we don’t have pre / post workflows, FWIW

pre/post workflows aren't a hard requirement for the issue but exponentially increase the possibility of hitting this issue since there are multiple clone operations

I’m assuming disabling autoplan won’t break cases where we’re relying on the autoplan modules feature for implicit module deps? That is, right now, our config has

- dir: foo/bar
    autoplan:
      enabled: false

for everything - assuming it would be pretty much the same if we set

ATLANTIS_DISABLE_AUTOPLAN="true"

and then just had

- dir foo/bar

for each state