Currently, the CLI mostly store the output of a command to files (SP-Config, transforms, reports, etc.)
This prevents from piping the output between different set of commands (jq, grep, etc.) or readability (after all, JSON is not that readable).
Azure CLI does have a --output/-o parameter (cf. https://learn.microsoft.com/en-us/cli/azure/format-output-azure-cli) that allows different type of format for any output.
It also has a --query allowing JSONPath filtering/transformation so we do not have to rely on jq or requivalent.
Finally, it is possible to define a default output.
SailPoint CLI would greatly benefit from such capability.
Currently, the CLI mostly store the output of a command to files (SP-Config, transforms, reports, etc.)
This prevents from piping the output between different set of commands (jq, grep, etc.) or readability (after all, JSON is not that readable).
Azure CLI does have a
--output/-oparameter (cf. https://learn.microsoft.com/en-us/cli/azure/format-output-azure-cli) that allows different type of format for any output.It also has a
--queryallowing JSONPath filtering/transformation so we do not have to rely on jq or requivalent.Finally, it is possible to define a default output.
SailPoint CLI would greatly benefit from such capability.