sherlock-distributed-lock
sherlock-distributed-lock copied to clipboard
Make failed migration behaviour configurable
Context
Whenever migration fails then it's lock is being released. I'd like to make this behaviour configurable.
Expected Behavior
It's great to fail in the development stage, but if for some reason the migration fails in production, then I'd like to keep the lock to avoid further issues.