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

add JSON debugging output #156

Open
ktdreyer opened this issue Apr 2, 2019 · 2 comments
Open

add JSON debugging output #156

ktdreyer opened this issue Apr 2, 2019 · 2 comments

Comments

@ktdreyer
Copy link
Member

ktdreyer commented Apr 2, 2019

For debugging, it would be nice to have some way to say "print all the JSON that the Errata Tool gives me".

This would be similar to koji's --debug-xmlrpc flag, or python-bugzilla's --debug flag.

We will need to add python logging, and print the JSON at the debug level.

@ktdreyer ktdreyer changed the title add debugging output add JSON debugging output Apr 2, 2019
@yazug
Copy link
Collaborator

yazug commented Apr 22, 2019

the pull request #159 addresses getting v1 api data, but as noted in review addition of unittests and doctext would be nice to get added

@yazug
Copy link
Collaborator

yazug commented Apr 22, 2019

I would say that this approach while nice should not be used for long term automation, and instead any features not exposed should be mapped through for parsing and consumption. This is so that tooling that works on errata-tool library has one layer of abstraction from implementation details. Over time ET has shifted and deprecated APIs and not all of the necessary fields that we currently parse work with are provided by the v1 api single call api.

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

2 participants