Separate Lock and Data file system locations

[jcarlson]

According to the documentation:

Atlantis has no external database. Atlantis stores Terraform plan files on disk. If Atlantis loses that data in between a plan and apply cycle, then users will have to re-run plan. Because of this, you may want to provision a persistent disk for Atlantis.

We tried deploying Atlantis to an AWS ECS Cluster and mounted an EFS volume as the “persistent disk”. Unfortunately, we discovered a well-known limitation of NFS-based storage in that Git repositories generally perform very poorly. git clone operations went from seconds to minutes.

It would be great if Atlantis could separate its use of the file system as a distributed lock from its use of the file system for cloning repositories. This would allow us to use the EFS share for persistent lock tracking, but configure an ephemeral, local volume for git cloning operations.

[ghostsquad]

@jcarlson do you have any more information on the "well-known limitation of NFS + Git" ?

[jcarlson]

https://www.jeffgeerling.com/blog/2018/getting-best-performance-out-amazon-efs

https://cloud.netapp.com/blog/efs-performance-dos-and-donts-aws-cvo-blg

https://stackoverflow.com/questions/4994772/ways-to-improve-git-status-performance

[lkysow]

Hi, I think this is a duplicate of #894