Manage infrastructure from behind a proxy

[kief]

I'm working in an office that only allows outbound http/s connections via a proxy. This currently prevents use with AWS provider, and I assume others as well. It would be useful to have a way to configure terraform (command line and/or config files) with the proxy details.

Thanks

[Filirom1]

+1

[lgs]

+1

[tkak]

+1

[wkielas]

As a temporary workaround I use iptables + redsocks to proxy outgoing terraform traffic, but real proxy support would be much better.

[ipolyzos]

+1

[justnom]

This is already supported natively by the Golang net/http package which aws-sdk-go uses.

To set an HTTP proxy just set either the HTTP_PROXY or HTTPS_PROXY environment variables.

On Windows:
set HTTP_PROXY=http://<your proxy address here>

On Mac/Linux:
export HTTP_PROXY=http://<your proxy address here>

Hope this helps :)

[phinze]

Yep @justnom is right - should be achievable via those environment variables.

[junessi]

+1

[spacemonkey]

+1

[ohmydata]

+1

[mikesimons]

I'm trying to inspect traffic coming from terraform-openstack-provider to debug some auth issues (using https://www.charlesproxy.com/) and it's totally ignoring the env vars. These requests are not showing up in Charles.

env http_proxy=http://127.0.0.1:8888 HTTP_PROXY=http://127.0.0.1:8888 HTTPS_PROXY=http://127.0.0.1:8888 https_proxy=http://127.0.0.1:8888 terraform plan

Grabbing the pid of a plugin process (8586 here) and inspecting the environment before it shuts down...

s> xargs -n 1 -0 < /proc/8586/environ | grep -i proxy
HTTPS_PROXY=http://127.0.0.1:8888
HTTP_PROXY=http://127.0.0.1:8888
http_proxy=http://127.0.0.1:8888
https_proxy=http://127.0.0.1:8888

So the plugin is getting the vars but they're not being used.

I think the problem (at least in the case of the openstack provider) is that you're overriding the transport passed to gophercloud but not setting Proxy from the env like the DefaultTransport does.

Each provider needs checking to ensure that it's either using the default transport or setting the proxy on its custom transport (AWS for instance uses go-cleanhttp which correctly sets proxies from env).

[pmithrandir]

Hello,

I'm using terraform behind a proxy, and I don't think it's working for openstack.
I get a time out each time I'm trying to reach my openstack platform, even if when using heat command it works.

Pierre

[pierrecarre]

+1

[danielcoman]

Hello,

I'm currently testing terraform and I'm also not able to get it working behind a corporate proxy with the openstack provider.

Daniel

+1

[TG-KK]

Not working with AWS provider too, even though variables are set

[kolly83]

Hello

Same here. Not working with AWS provider too, even though variables are set.

Although I was able to get it work once with the export proxy.

Any idea?

Thank you.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.