Skip to content
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

Use configured lock plugin for locking #1009

Open
soapy1 opened this issue Dec 4, 2024 · 0 comments
Open

Use configured lock plugin for locking #1009

soapy1 opened this issue Dec 4, 2024 · 0 comments

Comments

@soapy1
Copy link
Contributor

soapy1 commented Dec 4, 2024

Context

Follow up to #965 (persist the default lock plugin selection to the settings db table (and pull the default value from there))

Currently, there is only one lock plugin that can be used. In the future the selection of plugins will expand. So, users should be able to configure which plugin to use.

In order to do this, the locking plugin selection should be persisted to the settings db table. See #965 (comment) for an example of how an implementation for selecting a lock backend might look.

Depends on #1005

Value and/or benefit

Users can have a choice of which locking backend to use.

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: TODO 📬
Development

No branches or pull requests

1 participant