Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you use AWS CLI [0], you can embed JMESPath [1] queries via the --query switch, i.e. you don't ned jq. I was a loyal supporter of it, but switched to JMESPath [1], and I love its query languages more.

[0]: https://aws.amazon.com/cli/

[1]: http://jmespath.org/



Azure also uses this in their new CLI [0]. The biggest advantage of JMESPath over jq is that JMESPath is a spec, and thus can be implemented in several languages [1].

[0]: https://github.com/Azure/azure-cli [1]: http://jmespath.org/libraries.html


JMESPath is nowhere near us powerful. No unique(), for example, which is very important when munging JSON


Okay, but in 99.9% of the cases it's powerful enough.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: