Some users are in a corp network where all http traffic has to go through a proxy. bazelisk relies on http to talk to google storage API, github search API, and to download binaries.
It seems like at least support for the HTTP[S]_PROXY environment variables would be straightforward to add: https://golang.org/pkg/net/http/#ProxyFromEnvironment
If/when we have an npm package for bazelisk (#114) we should also read values from .npmrc to find the proxy config (https://docs.npmjs.com/using-npm/config#https-proxy) and pass that to the Go program. We can't tear down the @bazel/bazel npm package until this feature lands, because some users rely on the npm proxy setting to get Bazel onto their dev machines today.
Some users are in a corp network where all http traffic has to go through a proxy. bazelisk relies on http to talk to google storage API, github search API, and to download binaries.
It seems like at least support for the HTTP[S]_PROXY environment variables would be straightforward to add: https://golang.org/pkg/net/http/#ProxyFromEnvironment
If/when we have an npm package for bazelisk (#114) we should also read values from .npmrc to find the proxy config (https://docs.npmjs.com/using-npm/config#https-proxy) and pass that to the Go program. We can't tear down the
@bazel/bazelnpm package until this feature lands, because some users rely on the npm proxy setting to get Bazel onto their dev machines today.