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.

Sign up for GitHub

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

Jump to bottom

Engine - Update acquireTaskLock with prefix for Team or User context so that the lock is not system wide #382

Open

tlawrie opened this issue Mar 21, 2023 · 1 comment

Labels

bug

Member

tlawrie commented Mar 21, 2023 •

edited

Loading

The current acquireTaskLock is System wide as there is no context of User / Team / System that is passed in that needs to be available to make it specific. https://github.com/boomerang-io/flow.service.engine/blob/a733c7d2482161c6bca6113093a4b5febcb2f7a2/src/main/java/io/boomerang/service/LockManagerImpl.java#L52-L80

tlawrie added this to Boomerang Flow

tlawrie converted this from a draft issue

tlawrie added the bug label

Member Author

tlawrie commented Mar 21, 2023

Best solution would be to prefix field with a system parameter that is resolved before execution.

tlawrie moved this to To Do in Boomerang Flow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment