Closed mszostok closed 2 years ago
Currently, in most of our tutorials/documentations, we require from user to install the jq tools For example:
jq
capact typeinstance get {type-instance-id} -ojson | jq -r '.[0].latestResourceVersion.spec.value'
this can be simply replaced with:
capact typeinstance get {type-instance-id} -ojsonpath='.[0].latestResourceVersion.spec.value'
After https://github.com/capactio/capact/issues/489 it would be as simple as:
capact typeinstance get {type-instance-id} -ojsonpath='.spec.value'
We can re-use solution implemented in kubectl: https://github.com/kubernetes/cli-runtime/blob/e2af539b53266cfd3ee268922d3027f83de1e80a/pkg/printers/jsonpath.go#L139-L145
kubectl
Requires installation of external tools for most of the happy path scenarios. This should be simplified and Capact CLI should be the only one which is needed. One 💍 to rule them all 😎 . Same as we did for https://github.com/capactio/capact/issues/328 and https://github.com/capactio/capact/issues/466.
jsonpath
Description
Currently, in most of our tutorials/documentations, we require from user to install the
jq
tools For example:this can be simply replaced with:
After https://github.com/capactio/capact/issues/489 it would be as simple as:
We can re-use solution implemented in
kubectl
: https://github.com/kubernetes/cli-runtime/blob/e2af539b53266cfd3ee268922d3027f83de1e80a/pkg/printers/jsonpath.go#L139-L145Reason
Requires installation of external tools for most of the happy path scenarios. This should be simplified and Capact CLI should be the only one which is needed. One 💍 to rule them all 😎 . Same as we did for https://github.com/capactio/capact/issues/328 and https://github.com/capactio/capact/issues/466.
Use cases
Acceptance Criteria
jsonpath
output for all commands