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 proxy support and the ability for clients to override the HTTP timeout #926
Comments
4 tasks
kim-tsao
changed the title
Devfile Library: Add proxy support and the ability for clients to override the HTTP timeout
Add proxy support and the ability for clients to override the HTTP timeout
Sep 12, 2022
This was referenced Sep 12, 2022
kim-tsao
added a commit
to kim-tsao/registry-support
that referenced
this issue
Sep 19, 2022
…evfile/api#897 Signed-off-by: Kim Tsao <ktsao@redhat.com>
3 tasks
kim-tsao
added a commit
to devfile/registry-support
that referenced
this issue
Sep 19, 2022
…evfile/api#897 (#139) Signed-off-by: Kim Tsao <ktsao@redhat.com> Signed-off-by: Kim Tsao <ktsao@redhat.com>
re-opening for backports |
5 tasks
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/kind bug
Which area this bug is related to?
/area library
/area registry
Bug Summary
Describe the bug:
Dev console is running into issues creating an app in a disconnected cluster with a proxy using our Go devfile sample. The problem is with the parent devfile reference which the parser needs to read but because the HTTP client we construct does not contain proxy support, this action fails. We should also allow clients to override the default http request/response timeouts - default timeout of 30s has shown to be way too long of a wait (true for both the parser and registry library)
To Reproduce:
Expected behavior
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.
Additional context
Any workaround?
Suggestion on how to fix the bug
The text was updated successfully, but these errors were encountered: