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

Initial suggestion for Global locking for Timed Services #3092

Merged
merged 1 commit into from
May 16, 2024

Conversation

preardon
Copy link
Member

Issue #3075

This is an example of providers to allow locking across resources, included is

  • In Memory Lock (for when we only want a lock in process)
  • Azure Blob Lock

Copy link
Member

@iancooper iancooper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks spot on to me

@preardon
Copy link
Member Author

We should talk about merging some of the packages, given the size of the archiver and the and locking it could be worth just having an azure package

Issue BrighterCommand#3075

This is an example of providers to allow locking across resources,
included is

- In Memory Lock (for when we only want a lock in process)
- Azure Blob Lock
@preardon preardon merged commit a74571c into BrighterCommand:master May 16, 2024
16 of 17 checks passed
@preardon preardon deleted the distributedLock branch May 16, 2024 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants