fix(api/schedule): make validateEntry more strict and set updated_by using claims #901
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.
Prior to this change, the entry
0 1,2,10,12 * * *with aVELA_SCHEDULE_MINIMUM_FREQUENCYof180mwould be considered valid if you added the schedule between the hours of 12:00 Zulu time and 1:00 Zulu time the next day. Won't catch all cases, but I figured it would catch more than enough.Also set
updated_byin the update schedule endpoint.