Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request closes [#186] and brings in a resque-scheduler style dynamic schedules feature, allowing you to add or remove recurring tasks at runtime without touching your static config file.
What’s new:
SolidQueue::RecurringTask
model.SolidQueue::Scheduler::RecurringSchedule
to distinguish static vs. dynamic schedules.@configured_tasks
now includes both static and dynamic tasks.SolidQueue::Scheduler::RecurringSchedule.update_scheduled_tasks
:SolidQueue::Configuration
no longer requires a non-blank static config file - pure dynamic scheduling is now supported.SolidQueue::Scheduler
watches for changes after launch and updates its metadata so the running process always reflects the true set of recurring tasks.Tests verify that adding or dropping dynamic tasks at runtime correctly updates what’s scheduled.