In bug #1195990, we're porting all cronjobs to celerybeat-managed tasks. This bug covers converting update_feed to a celerybeat-managed task.
update_feed is defined in kuma/feeder/ app and the code is entirely in kuma/feeder/management/commands/update_feed.py . I think to convert it to a celerybeat-managed task, we need to: 1. move the code out of the management command code; maybe some of it belongs in the Feed model and the rest in a celery task or set of tasks--one per feed? 2. add tests--this app has no tests So, the feeder app has no tests and no docs. I'm not really sure what it does or how it fits in with the big picture. Do we even need it anymore? Maybe we can just nix it?
I talked with Jannis for a bit about possible AWS futures and how scheduled tasks might work. Most of the AWS futures involve something kicking off shell commands at specified times. Given that we decided it doesn't make sense to spend time converting everything to celerybeat. Given that, I'm WONTFIXing this bug.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.