Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[BUG]: ops cannot reach a local apihost behind a proxy

Abierto Apto para principiantes
  • ¿Algo no está bien?
#282 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bun, go, python
Área
cli, networking

Línea de trabajo

Sigue las referencias a issue #175 y openserverless-cli PR #56, y luego rastrea cómo ops configura apihost y pasa las variables de entorno del proxy a los comandos secundarios. Reprodúcelo con un devcluster local y HTTP_PROXY/HTTPS_PROXY configurados mientras NO_PROXY está vacío. Se considera completado cuando las solicitudes al apihost local omiten el proxy, mientras que las solicitudes remotas siguen usándolo.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

  • I have searched the issues of this repository and believe that this is not a duplicate.
Ⅰ. Issue Description

following up on #175 and https://github.com/apache/openserverless-cli/pull/56

The issue was that when HTTP_PROXY/HTTPS_PROXY are set, ops cannot talk to a local OpenServerless installation (eg. the devcluster at http://miniops.me, which resolves to 127.0.0.1). commands like ops ide deploy and ops env list failed, showing a ambigous error like repeat login.

The proxy variables themselves are honoured fine, go (ops -wsk, go-git), bun and curl all pick them up. so the suspection that the env vars propogation was the main culprit was wrong. the actual problem is that ops never sets its apihosts to NO_PROXY, so requests to the local apihost are also sent to the proxy, and the proxy cannot reach the developer's own machine. proxy for remote apihost worked fine, even before the fix.

Ⅱ. Describe what happened

with a forward proxy configured and no NO_PROXY, every request to the apihost goes to the proxy (even the local ones, that made it through a Repeat lgoin error. The proxy refuses the loopback target, so ops thinks the login is broken.

apache/issue175-test/proj 
❯ export HTTP_PROXY=http://172.18.0.1:3128 HTTPS_PROXY=http://172.18.0.1:3128 NO_PROXY=

apache/issue175-test/proj 
❯ ops ide deploy --packages
Repeat the login
ops: Failed to run task "deploy": exit status 1
task execution error: ops: Failed to run task "deploy": exit status 1
Ⅲ. Describe what you expected to happen

ops should work behind a proxy against a local installation, reqs to the local apihost go direct (bypassing the proxy, this can be done by appending the local apihost to NO_PROXY, everything else (github for ops -update, image registries,...) keeps going through the proxy.

Ⅳ. How to reproduce it (as minimally and precisely as possible)
  1. ops setup devcluster and ops ide login openserverless http://miniops.me (no proxy yet).
  2. run a forward proxy that the shell can reach. (i'll attach the one i used below in the comments).
  3. export HTTP_PROXY=http://<proxy>:3128 HTTPS_PROXY=http://<proxy>:3128.
  4. in a sample project run ops ide deploy --packages fails, (i've already attached a bash output above for this).
  5. ops env list fails as well.
Ⅴ. Anything else we need to know?

this happened beause ops passes its environment to every child (wsk, bun, curl in tasks) and none of these bypass the proxy for a hostname unless it is in NO_PROXY. Go for example only auto-bypasses literal localhost/loopback IPs, not a name that resolves to one. Nothing in ops sets NO_PROXY, so the apihost is never excluded.

Ⅵ. Environment:
  • K8S Runtime and version: kind (docker), Kubernetes v1.33.1, ops setup devcluster
  • OPS CLI version: 0.9.0-incubating (0.9.0 branch, 2026-10 snapshot)
  • Others: linux
Lenguaje dominante
Python
Estrellas
577
Forks
29
Merge medio
4 d 23 h
PR fusionados (30 d)
3

Preparar el entorno

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.

Más de apache/openserverless

Todos los issues de apache/openserverless

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.