The Wayback Machine - https://web.archive.org/web/20210711101134/https://github.com/zalando/zally/issues/925
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

Support JSON as output format for the zally CLI #925

Open
ahochsteger opened this issue Feb 14, 2019 · 3 comments
Open

Support JSON as output format for the zally CLI #925

ahochsteger opened this issue Feb 14, 2019 · 3 comments

Comments

@ahochsteger
Copy link

@ahochsteger ahochsteger commented Feb 14, 2019

It would be helpful, if the Zally CLI would support JSON as output format (--format json) to be easier to use in CI builds that need to post-process the output report.
Directly using the API is currently not a good option since the API is not able to directly consume the API spec files since they have to be wrapped into another JSON structure (api_definition_string).

@roxspring
Copy link
Collaborator

@roxspring roxspring commented Feb 14, 2019

Note that JSON output has previously been discussed under #648 with the conclusion that programmatic access should be using the API directly rather than via the CLI. Will be interesting to see if a different conclusion arises this time :)

Perhaps a preferable solution would be to add a new simpler API variant allowing the client to simply POST a raw spec file at the endpoint, without reference to api_definition_url or ignore_rules, which I suspect is the predominant way the service is used anyway.

@ahochsteger
Copy link
Author

@ahochsteger ahochsteger commented Feb 14, 2019

Yes, that sounds good to me.

@tkrop
Copy link
Member

@tkrop tkrop commented May 27, 2021

API access is still much more complicated than necessary. Unless we simplify the API, I'm open for contributions, that simply forward the response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment