Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Output parameter #59

Open
yannick-beot-sp opened this issue Apr 13, 2023 · 2 comments
Open

[Feature] Output parameter #59

yannick-beot-sp opened this issue Apr 13, 2023 · 2 comments

Comments

@yannick-beot-sp
Copy link

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.

@colin-mckibben-sp
Copy link
Contributor

@luke-hagar-sp We should look into this. We could probably just update all the list/get/download commands to print to stdout if no filepath is provided. I don't think that will be a breaking change. Thoughts?

@LukeHagar
Copy link

I'm thinking a global configuration option to specify output preference, standardized output formats supported via STDOUT, we would need to adjust some commands to allow for a more standardized output vs what is already implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants