3 ms·
One cool feature of the juniper junos CLI is that all the CLI commands have an option for XML output, making parsing of the CLI output in scripts a little more
by salem 15y ago
One cool feature of the juniper junos CLI is that all the CLI commands have an option for XML output, making parsing of the CLI output in scripts a little more sane.
- rch 15y agoI've started adding an option to output a complete Galaxy tool config file for some CLI apps. -- http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax
- shabble 15y agoThere was a project mentioned on HN fairly recently (~weeks ago) about an extended pipe system, using JSON and a bunch of common schemas, as I recall. Both http://acko.net/blog/on-termkit http://acko.net/blog/on-termkit and http://blogs.perl.org/users/rocco_caputo/2011/05/apppipefilters---json-in-the-shell.html http://blogs.perl.org/users/rocco_caputo/2011/05/apppipefilt... seem to fit what I was thinking of, but I'm sure there was something else. Nice ideas, but the inertia of existing unix tools is going to be hard to overcome, and a system isn't much use until all your common tools support it (or at least don't break it).
- killerswan 15y agoI talked some folks into using JSON output for a tool, and am now in the midst of fixing both ends so that the output is valid JSON, instead of a newline delimited file with JSON on each line.......