Slurp it up with the -s option. $ jq -s ‘.’ <<< ‘{ “a”: 1 } { “b”: 2 }’ [ { “a”: 1 }, { “b”: 2 } ] As another option, reading the values using inputs is a much more flexible alternative. You’ll usually want to use this in conjunction with the -n …
By default, jq formats its output to be a valid JSON value. This means that character strings are wrapped in quotes. Fortunately, the –raw-output or -r parameter overrides that behaviour so your string output can be free of those nasty quotation marks.
You need to call join() on the tags list, not the individual tags. Try with: jq -r ‘.tickets[] | [.created_at, .id, .via.channel, (.tags | join(“,”))] | @csv’
Yes; wrap the filter in an array 🙂 $ jq ‘[.[] | select(.id == “second”)]’ tmp.json [ { “id”: “second”, “val”: 2 }, { “id”: “second”, “val”: 3 } ] Or, use map/1, which is predefined as [.[] | …]. $ jq ‘map(select(.id == “second”))’ tmp.json [same result] To wrap the results in a bash …
I managed to figure it out. $ jq ‘.[] | { id, “info-spec”: .stuff[“info-spec”] }’ xample.json { “info-spec”: 12, “id”: 12345678 } { “info-spec”: 23, “id”: 12345679 } The key here seems to be to use the newkey: .complex[“key”] notation for lifting.
You have some extra quotes in there and test1 needs to be [“test1”] jq “.environments.${Environment_Name} += [\”test1\”]” tmp.json
You can try the great jq tool for parsing JSON in the shell. To de-pretty print with jq, you can use either method below: cat pretty-printed.json | jq -c . jq -c . pretty-printed.json the -c (or –compact-output) tells it to not pretty print (which is the default). The “.” tells it to return the …
You can use index to get the value of that key (wrapped for readability); docker inspect \ –format ‘{{ index .Config.Labels “com.docker.compose.project”}}’ \ new_sc2_1 That should give you the name of the project
In short – yes, except maybe for the one-liner bit. jq is often well-suited to text wrangling, and this is especially true of versions with regex support. With regex support, for example, the trimming required by the given problem statement is trivial. Since jq 1.5rc1 includes regex support and has been available since Jan 1, …
The answer to the original question is to use the filter .[] together with the -c command-line option: $ jq -c ‘.[]’ If the input file is very large (notably, if it is too large to fit into memory), it may be better to use jq’s –stream command-line option, or a companion tool. If the …