Allow seconds in cron string settings #10
Merged
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.
The syntax for specifying seconds in a cron job is not standardized, as traditional Unix cron does not include a field for seconds. For more information, see https://en.wikipedia.org/wiki/Cron#Cron_expression.
We currently use two libraries with different approaches to specifying seconds:
croniter
: https://github.com/kiorky/croniter/blob/master/src/croniter/tests/test_croniter.py#L39* * * * * */15: Every 15 seconds
cron-descriptor
: https://github.com/Salamek/cron-descriptor/blob/master/tests/TestFormats.py#L59*/15 * * * * *: Every 15 seconds
This pull request removes the cron description from the Admin interface and drops the
cron-descriptor
library from the requirements. Instead, the syntax ofcroniter
is used, as it ensures that configurations without seconds are still compatible.