New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Invalid Header Failure with Chef Environment #8382

Closed

tacchino opened this issue Aug 22, 2016 · 4 comments

Labels

bug provider/chef

tacchino commented Aug 22, 2016

Receiving a failure with chef_environment on Terraform v0.7.1 during a terraform plan.

Error refreshing state: 1 error(s) occurred:

* chef_environment.env: Get https://api.opscode.com/organizations/xxx/environments/staging: net/http: invalid header field name "Hashed Path"

Works fine with v0.7.0

Terraform v0.7.1
chef_environment

The text was updated successfully, but these errors were encountered:

catsby added provider/chef bug labels

donaldguy commented Aug 22, 2016

I saw the same thing in TF_LOG=INFO output of a (still running) terraform refresh but with respect to a data bag.

donaldguy commented Aug 22, 2016

Seems like the vendor needs to be updated to pull in go-chef/chef#75

seems to relate to switch from a go1.5 to a go1.6 compilation?

donaldguy mentioned this issue

vendor: update go-chef, fixes #8382 #8401

Merged

Contributor

mitchellh commented Aug 26, 2016

Fixed by #8401

mitchellh closed this as completed

mitchellh pushed a commit that referenced this issue


          vendor: update go-chef, fixes #8382

36b4b1a

mitchellh added a commit that referenced this issue


          Merge pull request #8401 from donaldguy/vendor-update-chef

16bedd8

vendor: update go-chef, fixes #8382

richardbowden pushed a commit to richardbowden/terraform that referenced this issue


          vendor: update go-chef, fixes hashicorp#8382

8d1fa28

ghost commented Apr 22, 2020

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.

ghost locked and limited conversation to collaborators

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.