|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
pingou commented 3 years ago | ||
|
||
|
||
|
||
|
||
|
||
|
||
pingou commented 3 years ago hm, anyway we could package this as RPM, include it in the infra repo and install it this way instead of from git/pip? (+ I know how much you love RPM :)) | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
This should automate running the "countme" scripts every day to parse new log data and publish updated totals.
There's more detailed info in commit e6376b9, but here's a couple notes:
prod
branch of https://pagure.io/mirrors-countme. I've seen that pattern used elsewhere in the playbooks, so I think that should be OK here?countme
instead of root wherever possible. That's different from how the other scripts run, but it seems like a good idea.totals.csv
in a private git repo isn't required but it also seemed like a good idea to have complete history of changes to the data we publish - especially if we later end up changing the counting algorithms or something. Good for accountability!I ran the YAML changes through ansible-lint
and it came out OK, and I tested the scripts manually and they're running fine.
But: this is my first attempt to modify any of our playbooks, so.. sanity checks and close reviews might be a good idea. OK thanks!
Is that going to re-clone everytime or will it also fetch/update if the clone already exists?