Schedule fullDataScan weekly via Celery Beat#45
Merged
Conversation
Runs every Sunday 03:00 UTC alongside the existing daily purge_stale_profiles schedule. The admin-triggered datascan endpoints are kept for ad-hoc manual scans.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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
CELERY_BEAT_SCHEDULEentry forfullDataScan, running weekly (Sunday 03:00 UTC) alongside the existing dailypurge_stale_profilesschedule./api/custom/datascan/endpoints (full and per-category) are kept as-is for ad-hoc manual scans.Test plan
pytest tests/— 33 passedruff check/ruff format --check— cleanweb/beatcontainers and confirmedsettings.CELERY_BEAT_SCHEDULEloads the new crontab entry withBLIZZ_CLIENT/BLIZZ_SECRETpopulated;beatcontainer starts cleanly with no errors