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.

Sign up for GitHub

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

Jump to bottom

Flag or verbosity level to dump http request/response #189

Open
richardcase opened this issue Nov 13, 2020 · 0 comments
Open

Flag or verbosity level to dump http request/response #189

richardcase opened this issue Nov 13, 2020 · 0 comments
Labels
area/cli Related to the CLI plumbing help wanted Extra attention is needed kind/feature A new feature request priority/backlog Higher priority that awaiting-more-information. This issue is on the backlog for future development.
Projects
kconnect planning
Milestone
Future

Comments

@richardcase
Copy link
Contributor

Describe the solution you'd like:
I'd like to have a flag or verbosity level that will dump the http request/response bodies if enabled

Why do you want this feature:
To debug issues with HTTP requests.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
@richardcase richardcase added help wanted Extra attention is needed kind/feature A new feature request priority/backlog Higher priority that awaiting-more-information. This issue is on the backlog for future development. area/cli Related to the CLI plumbing labels Nov 13, 2020
@richardcase richardcase added this to the Future milestone Nov 13, 2020
@richardcase richardcase added this to Backlog in kconnect planning via automation Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/cli Related to the CLI plumbing help wanted Extra attention is needed kind/feature A new feature request priority/backlog Higher priority that awaiting-more-information. This issue is on the backlog for future development.
Projects
kconnect planning
  
Backlog
Milestone
Future
Development

No branches or pull requests
1 participant
@richardcase