Skip to content
This repository has been archived by the owner on Dec 5, 2020. It is now read-only.

Chef Provider: Proxy not seeing #3

Open
hashibot opened this issue Jun 13, 2017 · 0 comments
Open

Chef Provider: Proxy not seeing #3

hashibot opened this issue Jun 13, 2017 · 0 comments
Labels

Comments

@hashibot
Copy link

This issue was originally opened by @gopisaba as hashicorp/terraform#5898. It was migrated here as part of the provider split. The original body of the issue is below.


Hi Team,

I am using terraform to build AWS and Chef infrastructure. From company laptop we have strict security policies and using proxies to connect to internet. We have set environment variables like http_proxy and https_proxy to connect to the AWS and chef servers.

The problem is terraform can able to connect to the AWS but not to the Chef server.

`module.production.chef_environment.environment: Refreshing state... (ID: production)
Error refreshing state: 1 error(s) occurred:

  • chef_environment.environment: Get https://api.chef.io/organizations/xxxxx/environments/production: dial tcp 52.20.79.149:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time or established connection failed bec
    ause connected host has failed to respond.`

I am able to connect to the Chef server via knife command and GUI but not with the help of terraform. Looks like terraform-chef provider is not seeing the http_proxy and https_proxy like terraform-aws provider. I could able to replicate the same problem in different machines as well.

@hashibot hashibot added the bug label Jun 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant