[01:09:11] * bd808 off [10:00:48] working on the `toolforge build quota` command. if this is the "regular" output, what would you expect json version to look like? Like the json equivalent of the "regular" output, or like the underlying json-object, i.e. quota_info = {"quota": {"hard": {"storage": 5368709120}, "used": {"storage": 984430250}}} https://usercontent.irccloud-cdn.com/file/pRmsR7oM/Screenshot%202023-11-22%20at%2010.56.36.png [10:04:44] like the output [10:05:00] blancadesal: this is what jobs-api does, I quite like it: https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-api/-/blob/main/tests/helpers/fixtures/quota/expected-api-result.json [10:12:54] ok, I should probably have the api return a similarly nice object then have only some minimal logic on the cli side dealing only with display. Instead of what I'm doing now, which is passing on the raw (stripped-down) response from the harbor API and doing all the work on the frontend. [11:44:29] jbond: is it known that on a cloud vps puppet 7 puppetaster, the git repo update timer does not run g10k to update /srv/puppet_code/? [11:47:14] taavi: no thats unexpected let me double check [12:15:41] taavi: https://gerrit.wikimedia.org/r/c/operations/puppet/+/976690/ [12:49:07] taavi: thanks for pointing me to the jobs api. How does this output format look to you? https://usercontent.irccloud-cdn.com/file/YZ6gkIlw/Screenshot%202023-11-22%20at%2013.47.39.png [12:50:05] jbond: thanks, will look in a sec [12:51:18] cheers [13:16:11] blancadesal: I would try to fit everything in a single category to a single table, instead of having a table per item. but the json representation seems fine [13:17:32] 👍 thanks for the feedback [13:42:39] taavi: when you have a moment, could I get a quick review of https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-api/-/merge_requests/60 ? [13:51:13] taavi: thanks for the review i hav merged that now.