4 ms·
And rq has even easier syntax.
by jedisct1 9y ago
And rq has even easier syntax.
- cryptonector 9y agoLink?
- bklaasen 9y agohttps://github.com/dflemstr/rq/blob/master/README.md https://github.com/dflemstr/rq/blob/master/README.md
- cryptonector 9y agoThanks!
- erric 9y agoNever had heard of rq, so thanks to the person above for that. I also use jp from JMESpath. I like it because both azure and aws cli use the JMESpath way of dealing with JSON so filtering between two different cloud providers is at least a _little_ easier when hunting needles in haystacks. For some compare and contrast between: jsonpath, jq, and jp these were for getting AWS ec2 instance IDs: cat foo.json | jsonpath -p $.InstanceProfiles.[*].RoleId cat foo.json | jq .InstanceProfiles[].Roles[].RoleId cat foo.json | jp InstanceProfiles[].InstanceProfileId apologies to mobile users!
- stormbrew 9y agoI.. really don't agree. I had to use rq because I was working with a toml file and I could not for the life of me figure out even the basic things I was trying to do. The documentation was sparse and unclear compared to jq's relatively concise but clear documentation. In the end I wound up just using rq to convert the toml to JSON so I could use jq on it. It was a while ago so I suppose it's possible I just used it too early in its life or something though.