Skip to content

Leverage EFS to persist atlantis locks between deployments? #206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mwarkentin opened this issue May 10, 2021 · 7 comments · Fixed by #247
Closed

Leverage EFS to persist atlantis locks between deployments? #206

mwarkentin opened this issue May 10, 2021 · 7 comments · Fixed by #247

Comments

@mwarkentin
Copy link
Contributor

Is your request related to a problem? Please describe.

Every time we make a change that requires redeploying our atlantis container, we lose all of the locks on PRs that atlantis currently has. These locks are persisted to the file system which is not maintained between containers.

Describe the solution you'd like.

I'm wondering if the module could configure an EFS mount where the file system locks can be maintained, so that they persist between deployments.

Describe alternatives you've considered.

Currently we have to capture the current list of locks, deploy atlantis, and then go to each of the PRs to reacquire the locks.

@github-actions
Copy link

github-actions bot commented Jan 7, 2022

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Jan 7, 2022
@mwarkentin
Copy link
Contributor Author

Stayin' alive..

@MarkIannucci
Copy link
Contributor

I have some work underway to fix this issue in the PersistInEFS branch in my fork.

With the Ephemeral storage functionality introduced in #229, I'm a bit torn on how to proceed. My feeling is that we'd want to use EFS by default if the configuration doesn't indicate the user's intent to use larger Ephemeral storage, and that is the direction that I plan to use, unless I hear otherwise.

I also had to adjust the max and minimum deployment percent variables to 100 and 0 respectively because Atlantis gets angry if the BoltDb is in use when it gets turned on. This means that redeployments now cause short outages (in my experience less than 5 minutes). I think that's a better situation than issue identified here where data gets lost if the container terminates for any reason. Ultimately, the short outage issue will get fixed by #19.

@MarkIannucci
Copy link
Contributor

@mwarkentin , I submitted #247 a few days ago. I've been running it for my personal repos over the last two weeks, and I've been happy with it. I don't know if you want to give it a shot in your environment. If you do and want to share your results I think it will provide another helpful datapoint for the PR which will increase everyone's confidence :-)

@mwarkentin
Copy link
Contributor Author

@MarkIannucci thanks! I'll check with the team, I'm not responsible for Atlantis at our company anymore. Looks like there are some code review requests from Anton though. :)

@antonbabenko
Copy link
Member

This issue has been resolved in version 3.10.0 🎉

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants