Re:JSON on the Command Line with Jq
by dastx on Sunday December 22, 2019 @07:01PM
(#21860522)
If you're using AWS you're better using the built in option available for the cli. The --query option (and often combined with the --output option) does this, and uses JMESPath. Especially when you're scripting, it eliminates the need for having yet another tool.
[ Parent
| on HN ]
Re:JSON on the Command Line with Jq
by dragonwriter on Monday December 23, 2019 @01:35AM
(#21861872)
> If you're using AWS you're better using the built in option available for the cli. The --query option (and often combined with the --output option) does this, and uses JMESPath.
Jq is so much more capable than jmespath that I find myself using jq on the json output of AWS CLI commands more than using the built-in query option. Sure, it requires another tool, but it’a often the best tool for the job.
That's a great point. Leverage --query for good justice.
Unless you need some additional juice, where jq supports actually transforming the return.
Quite arguably a heavier tool, e.g. a boto3 script becomes appropriate where --query falls short.
But options are a great thing to have.