-
Notifications
You must be signed in to change notification settings - Fork 498
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
Feature - refactor cron formatting #336
Comments
A good idea IMO. But with the in-memory you could run into memory bottlenecks as we scale to 10,000 -100,000 repository. Will the solution be an issue for such scales? |
Depends on how we handle the results. We could keep writing to file/DB every time a result comes back or we can batch it to reduce IO. But yes, we mostly will not hold all results in memory at the same time. |
SGTM. |
Big +1 for this :) This would clean up a lot of how the current outputting is done. |
Is your feature request related to a problem? Please describe.
The cron job appends the output of scorecard commandline to an output. This is a problem since, the cron job deals with string output from the scorecard command and tries to get the formatting right.
Describe the solution you'd like
Instead, the cron job should be dealing with in-memory data structure of check results which it can use in any way it likes, including formatting it using pre-existing formatting libraries (like JSON). To do this, we need to refactor such that we have a common library of functions/types which will be used by both the commandline tool as well as the cron job.
@inferno-chromium - this is a fair amount of refactor work, but IMO worth the time/effort. Let me know if this LG to you and I can get started on it.
The text was updated successfully, but these errors were encountered: