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.

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

Allow recuring tasks to be configurable #34

Closed
Jericho opened this issue Jan 7, 2024 · 2 comments
Closed

Allow recuring tasks to be configurable #34

Jericho opened this issue Jan 7, 2024 · 2 comments
Assignees
@Jericho
Labels
Enhancement New feature or request
Milestone
9.0.0

Comments

@Jericho
Copy link
Owner

Jericho commented Jan 7, 2024

Developers should be able to customize how frequently recurring task are executed and we should set sensible default values.
@Jericho Jericho added the Enhancement New feature or request label Jan 7, 2024
@Jericho Jericho added this to the 9.0.0 milestone Jan 7, 2024
@Jericho Jericho self-assigned this Jan 7, 2024
@Jericho
Copy link
Owner Author

Jericho commented Jan 7, 2024

Specifically, developers should be able to configure:

  • how often the message pump fetches messages from Azure queues (default: one second)
  • how often the message pump counts how many messages are pending in Azure (default: 5 seconds)
  • how often the message pump counts how many messages are in memory, waiting to be processed (default: 5 seconds)
  • how often the multi-tenant message pump fetches the list of queues that match the naming convention (default: 30 seconds)

@Jericho Jericho closed this as completed in b4336d3 Jan 7, 2024
@Jericho
Copy link
Owner Author

Jericho commented Jan 30, 2024

🎉 This issue has been resolved in version 9.0.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

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

@Jericho Jericho

Labels
Enhancement New feature or request
Projects
None yet
Milestone
9.0.0
Development

No branches or pull requests
1 participant
@Jericho