Never 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 dea

Never 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!