4 ms·
I wonder how they will address versions… `aws s3 ls | jc —-aws=1.2.3` What a nightmare.
by alex_suzuki 3y ago
I wonder how they will address versions…
`aws s3 ls | jc —-aws=1.2.3`
What a nightmare.
- dj_mc_merlin 3y agoWhat about jc 'aws sts get-caller-identity' | jq [..] That way the aws process can be a subprocess of jc, which can read where the binary is and get its version automatically.
- jasonjayr 3y agoThat can get thorny, because it adds another level of shell-quoting/escapes, and that is a notorious vector for security problems.
- sesm 3y agojc already has this, see ‘jc dig example.com’ in examples. They call it ‘alternative magic syntax’, but IMO it should be the primary syntax, while piping and second-guessing the previous commands parameters and version should be used only in exceptional cases.
- dtech 3y agoAws cli isn't the best example because it supports outputting json natively. I'd expect this to not be a huge problem in practice because this is mostly for those well established unix cli tools of which the output has mostly ossified anyway. Many modern and frequently updated tools support native JSON output.
- hnlmorg 3y ago> Aws cli isn't the best example because it supports outputting json natively. The s3 sub command annoyingly doesn’t. Which I’m guessing is the reason the GP used that specifically.