ayush00git commented on issue #175: URL: https://github.com/apache/openserverless/issues/175#issuecomment-6449544989
Thanks for the hint, I reproduced with `ops setup devcluster` behind a proxy (`HTTP_PROXY`/`HTTPS_PROXY` set, `NO_PROXY=localhost,127.0.0.1`, proxy refusing loopback targets like a corporate one does). The cluster deploys fine, but the final `ops setup openserverless login` loops for 600 s with HTTP status code 502: `wsk` sends `GET http://miniops.me/api/v1/namespaces` to the proxy, which can't reach miniops.me (127.0.0.1). Same for bun, `ops env list` sends its POST req to the proxy and fails with Error while making API request. Adding the `apihost` to the bypass list (NO_PROXY=localhost,127.0.0.1,miniops.me) makes both work immediately. So the env vars are propagated, `wsk`, bun and curl all honor HTTP(S)_PROXY/NO_PROXY the same way. the issue is so interesting, the issue is that ops never adds its own apihost to `NO_PROXY`, so requests meant for the local machine go to the proxy. Since ops sets the `apihost`, it should append it to `NO_PROXY` for the processes it spawns. I'll do the same in my local machine and test it, if it works fine i'll open a PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
