feat(jobs): allow optional cron on job.yml for UTC schedules - #282
Merged
Merged
Conversation
Add a Job cron shortcut that validates in metadata and materializes a file-backed Schedule during migrate so simple one-job schedules do not need a separate _schedules.yml entry. Co-authored-by: Cursor <cursoragent@cursor.com>
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
cronon Job metadata (job.yml) for the common one-Job UTC schedule casejob.cronduring metadata sync_schedules.yml(non-UTC or multiple schedules)Test plan
dygo db migratewith a Job that setscron: "…"creates/updates the matching Schedulecronis unchanged;_schedules.ymlschedules still workdygo workerenqueues and runs the materialized Schedule occurrencedb/schema.sqlandconfig/secrets/development.yml.ageare not in this PRCloses #214