-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(schedules): Rework daily schedule to always show the next scan #6700
feat(schedules): Rework daily schedule to always show the next scan #6700
Conversation
… and scheduled_at calculation
…scans-right-after-creating-a-provider
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6700 +/- ##
==========================================
- Coverage 93.52% 93.41% -0.11%
==========================================
Files 67 70 +3
Lines 6330 6412 +82
==========================================
+ Hits 5920 5990 +70
- Misses 410 422 +12
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just tested out the functionality and works as expected, thanks @vicferpoy 👏
…scans-right-after-creating-a-provider
a47652b
Description
With this development, daily schedules will always add a new
scheduled
scan, with the correctscheduled_at
datetime in its details. We are soft deprecating thenext_scan_at
field for it.In addition, we added a new Django migration to migrate the former scheduled scans to this "format".
When adding new providers for the first time, after requesting
POST /schedules/daily
, a newscheduled
scan withavailable
state will be created right away and will be executed once a worker is available, improving the UX.License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.