feat: allow using a pattern of file to specify multiple configurations of recurring tasks #620
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s of recurring tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Having only one file to configure recurring tasks is not optimal when handling several engines within the same codebase that are isolated from each other.
With these changes, it will be possible to define a pattern of config file paths (eg:
engines/*/config/solid_queue/recurring.yml).Note:
recurring_schedule_file? I can see a use case where transversal tasks are definedconfig/recurring.ymland others more oriented toward business topics are defined inengines/*/config/solid_queue/recurring.yml