Skip to content
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.

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

Remote state saved to artifactory using private CA authority fails on OSX #8127

Closed
mbreitung opened this issue Aug 10, 2016 · 4 comments
Closed
Labels

Comments

@mbreitung
Copy link

When using a private CA and using official terraform binaries, trying to set up remote state gives this error:

terraform remote config -backend=artifactory -backend-config="username=user1" -backend-config="password=xxxxx" -backend-config="url=https://artifactory.example.com/artifactory" -backend-config="repo=generic-terraform-state-files" -backend-config="subpath=test_path.us-west-2"

Error reloading remote state: Get https://artifactory.example.com/artifactory/terraform-state-files/test_path.us-west-2/terraform.tfstate: x509: certificate signed by unknown authority

Versions:
Terraform v0.6.16 or Terraform v0.7.0

The workaround is to clone and then compile terraform manually on OSX 10.11.6 (macbook pro):
$ go version
go version go1.6.3 darwin/amd64
$ git status
HEAD detached at v0.6.16
$ make dev

I now get success:
Initialized blank state with remote state enabled!

@brimstone
Copy link

This looks like an artifact of building for darwin on linux. There's a workaround described here:
https://inconshreveable.com/04-30-2014/cross-compiling-golang-programs-with-native-libraries/

@mbreitung
Copy link
Author

the main README states how to cross compile, that looks incomplete

https://github.com/hashicorp/terraform/blob/master/README.md

@hashibot
Copy link
Contributor

Hello! 🤖

This issue seems to be covering the same problem or request as #3536, so we're going to close it just to consolidate the discussion over there. Thanks!

@ghost
Copy link

ghost commented Sep 27, 2019

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 ghost locked and limited conversation to collaborators Sep 27, 2019
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

4 participants