Set-up feeders with `ignore-cursor` flag
Summary
We need time to time refresh database with the packages that might be overlooked. For this task we need to run feeder CI jobs with ignore-cursor
flag. We need to do it 1-3 times per month.
Problem
During an incremental round, we give each newly discovered {package, version}
a certain number of retries before giving up. Some of those errors are transient but will be stable around the same time: for example, if the remote server is under maintenance. With incremental scanning alone, we'd never reconsider that {package, version}
ever again.
Another orthogonal reason is if we improve our license detection logic: previously unknown packages might become detectable. Classifications mistakes in general can be fixed.
Implementation plan
- Create scheduled jobs for feeder similar to the ones that we have already for each package registry
- Add
IGNORE_CURSOR:true
flag to its ENV variables.
Edited by Philip Cunningham