It sounds like you're using this as an api, but Koji already has an api. This is just a convenience command.

Not using it as an API, just wanting to use jq to filter the output when using it as a convenience command. For debugging and development.

I've often had to do something that neither the Koji web interface nor the cli does, but only had to do it once or twice and then never again until I need to do something else entirely. Usually being able to parse the output with jq would have come in handy, because the output is too chatty.

You can think of this as a convenience feature being added to a convenience command. I'm not trying to do anything fancy here.

Ok, makes sense. Pulling this in.

Side note: it's best to avoid using your master branch for a pull-request

Commit 2941f9f0 fixes this pull-request