OpenAPITools / OpenAPITools/openapi-generator-cli

[BUG] The version manager does not respect the NO_PROXY environment variable.

Abierto
#652 1 comentario 7 reacciones 1 asignado Ver en GitHub

@kay-schecker ya está trabajando en esto.

Desde el 20/6/2022.

bug
Lenguaje dominante
TypeScript
Estrellas
2k
Forks
208
Merge medio
7 h 12 min
PR fusionados (30 d)
6

Descripción

🐛 Bug Report:

Describe the bug

The version manager does not respect the NO_PROXY environment variable. When using the openapi-generator-cli behind a corporate proxy (i.e. HTTP_PROXY & HTTPS_PROXY are set) while trying to download a version of openapi generator from a private maven repository (which is within the corporate network, i.e. the download should not go through the proxy), the NO_PROXY environment variable is ignored.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Use the openapi-generator-cli version manager to download a version from a private repository within a corporate network, which is separated from the internet by a proxy.
  2. openapi-generator-cli respects HTTP_PROXY & HTTPS_PROXY (which are needed for requests from within the corporate network to the internet, but fails to download from the internal maven repo, as it still tries to go through the proxy:
> openapi-generator-cli generate

Download 6.0.0 ...
Download failed, because of: "socket hang up"
  1. Only by explicitly un-setting the HTTP_PROXY & HTTPS_PROXY environment variables as a work-around it is possible to download from the private repo.
Expected behavior

The openapi-generator-cli version manager should respect the NO_PROXY environment variable and download the version of openapi generator from the private repo without going through the proxy.

Additional context

Also mentioned in these comments.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.