4 ms·
Using it for parsing AWS CLI responses, it's been a sweet tool to parse those JSON responses from AWS, most of the time I'd fire some python script to parse the
by piva00 12y ago
Using it for parsing AWS CLI responses, it's been a sweet tool to parse those JSON responses from AWS, most of the time I'd fire some python script to parse the data and now with jq I can keep most of the one-time scripts limited to bash only, if I need something more maintainable or longer living then I'll drop a script in python or ruby.
- bramgg 12y agoThat's exactly what I did with Pouch (https://github.com/bramgg/pouch https://github.com/bramgg/pouch).
- Terretta 12y agoJmesPath is built into the AWS CLI. You don't need separate JQ. See the --query option: http://docs.aws.amazon.com/cli/latest/userguide/controlling-output.html http://docs.aws.amazon.com/cli/latest/userguide/controlling-... Check out http://jmespath.org http://jmespath.org for details.
- piva00 12y agoOnly saw your comment today, thanks so much for this, I really overlooked this part from the docs.