-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
cannot use ResourceProvider as type ProviderFunc in field value #2077
Comments
Hi @nathanielks . I get the same error trying to build a plugin for terraform. Also on a fresh clone, on a commit that I can see passes travis tests!
|
Hi folks, As a quick review:
Thanks! |
@Ninir I think I found at least some of the problem. When I got the error reported above I did: Just now I did It seems I got the dir structure convention in go wrong (this is my first attempt to build go code). It has to be as in B2, not A1 |
I can confirm @jwermuth. I had to rename the directory to |
@Ninir can confirm my fork is in sync and am currently using Go 1.9.1. |
I had the same problem. |
@nathanielks I'm stuck on this problem as well. Did you figure out a work-around? @pawelsocha what do you mean by a vendor "refresh"? |
I forked 'terraform-providers/terraform-provider-aws' under my $GOPATH/src/github.com. It builds and allows me to do my provider development. Maybe the README section: "Developing the Provider" meant to include that one should fork in the same directory location as specified under "Building the Provider".... |
@thomaswhitcomb I'm trying to reproduce the problem on a new computer. |
Okey, I create full path in GOPATH
|
@thomaswhitcomb I just renamed the parent directory from |
I have a similar issue. I forked this repo, cloned it into
Maybe the issue is that terraform has vendored terraform-provider-aws and terraform-provider-aws has a dependency on terraform (and also has it vendored)? |
I change makefile on the forked repo to build provider everywhere ;P @iancward golang building process is strictly connected with GOPATH and sometimes it defaults to resolve dependencies from import block. |
The solution is to built terraform provider in |
The repository README does indeed list the solution mentioned above: https://github.com/terraform-providers/terraform-provider-aws/#building-the-provider
If there are indeed errors with the README instructions for building/testing, please do let us know! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Hey, team!
I'm trying to contribute but unfortunately tests are failing out of the gate. I haven't made any modifications to my fork of the repo at all. I cloned then ran
go get github.com/nathanielks/terraform-provider-aws
to download it.Terraform Version
Terraform v0.10.7
Debug Output
https://gist.github.com/nathanielks/8e2ac160c09258c4ece0ccb2f097a1ae
Expected Behavior
Tests should pass as I pulled off of master which should be stable.
Actual Behavior
Tests are failing with error:
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
go get github.com/nathanielks/terraform
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
The text was updated successfully, but these errors were encountered: