-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Usage of SQL Server for Locking #264
Comments
I would also like to add that it would be good to also suppose the cloud-native database like AWS DynamoDb. It is not a SQL-based database but service like AWS DynamoDB creates a minimal Ops maintenance overhead. |
@lkysow @anubhavmishra Can I get your blessing before taking this approach / working on this? |
Hi @sargun, I'm going to reach out to you to schedule a meeting because this is a large architectural change. Check your email :) |
Hi @Ikysow, I'd be interested in implementing this feature or a more general equivalent, could we get in touch? |
@samcgardner my comment here #265 (comment) talks about my opinion on this change at the moment. However I'm happy to chat. You can hit me up on the Atlantis Slack? |
I propose we introduce the usage of using a SQL server for locking.
I propose we do this by adding support for sqlite, and postgresql first.
I propose we do this by introduce the ability to say
--locker ${DATABASE_URI}
when initializing Atlantis.I propose that we use https://github.com/xo/dburl to parse the dburls and create the connections. If this URI is blank, we fall back to BoltDB.
I propose that schema management, at least for version 1 of this exercise is outside of the scope, and we add it to documentation on how to create, and / or migrate the schema. Later on, we can add a schema management tool.
Opinions?
The text was updated successfully, but these errors were encountered: