JC – JSONifies the output of many CLI tools
kellyjonbrazil.github.io
JC – JSONifies the output of many CLI tools
1–10 of 136 posts
Re: JC – JSONifies the output of many CLI tools
#2Command line output as JSON. Very handy and has parsers for tons of common utilities, written in Python.
Blog post with examples here: https://blog.kellybrazil.com/2020/08/30/parsing-command-outp...
Re: JC – JSONifies the output of many CLI tools
#3In the opposite direction, if you want to recover a human-editable text stream from json data, you run gron.
Re: JC – JSONifies the output of many CLI tools
#4Then pipe it into jq [1] to query parameters or build up a formatted string.
Or pipe it into rq [2] to convert the format to yaml, toml etc.
[1]: https://stedolan.github.io/jq/tutorial/ [2]: https://github.com/dflemstr/rq#format-support-status
Re: JC – JSONifies the output of many CLI tools
#5As someone who uses `jq` almost daily, this looks like a great tool I didn’t know I needed.
Thanks for the tip!
Re: JC – JSONifies the output of many CLI tools
#6love it, json could be the best way to pipe data between processes because it is text, but structured
Re: JC – JSONifies the output of many CLI tools
#7I stumbled upon this few weeks ago to parse the output of nmcli and now it is in my toolset for scripting
I love it
Re: JC – JSONifies the output of many CLI tools
#8Last year I looked for JSON output with the dig command on Linux but found the yaml option while reading the man page. It was handy. I always wondered why yaml/JSON output is not standard with Linux and Unix utilities for scripting needs. Anyway:
dig +yaml google.comRe: JC – JSONifies the output of many CLI tools
#9Been using this a while to pull out a bunch of server stats for a monitoring dashboard and it's been great. I just wish there were more supported services. The total mess of different outputs and config types for Linux packages is extremely annoying to deal with.
Re: JC – JSONifies the output of many CLI tools
#10Didn't know about this, the HN dividend pays out again!
When wrestling with sed/awk in trying to parse results of a shell command, I've often thought that a shell-standard, structured outpout would be very handy. Powershell[0] has this, but it's a binary format - so not human-readable. I want something in the middle: human- and machine-readable. Without either having to do parsing gymnastics.
jc isn't quite that shell standard, but looks like it goes a long way towards it. And, of course, when JSON falls out of fashion and is replaced by , `*c` can emerge to fill the gap. Nice.