3 ms·
The JSON expressions used by MySQL and the AWS command line tool (JMESpath) are extremely limited compared to jq. So not only do we end up learning multiple JS
by justin_oaks 4y ago
The JSON expressions used by MySQL and the AWS command line tool (JMESpath) are extremely limited compared to jq.
So not only do we end up learning multiple JSON path variations, but most of them are nearly useless for anything but the simplest use cases.
I appreciate the intention of including JMESpath in awscli, but I quickly dropped it in favor of piping the JSON results to jq.
- mdaniel 4y agoI have a similar complaint but I'd guess there are (at least) two problems standing in the way of awscli getting jq language support: a python impl of the language with a license that awscli tolerates, and awscli being (in general) very conservative about changes. There are innumerable open issues about quality of life improvements that are "thank you for your input" and I'd expect that change to be similarly ignored
- thayne 4y agoNot to mention that JMESpath appears to be abandoned. There is a fork (https://github.com/jmespath-community/jmespath.spec https://github.com/jmespath-community/jmespath.spec), but it seems unlikely to be used by the aws cli (https://github.com/aws/aws-cli/issues/7396 https://github.com/aws/aws-cli/issues/7396). Although, for that matter jq is semi-abandoned itself.
- deleted 4y ago[deleted]