This isn't really a bug, but I found this behavior surprising and thought it might be worthwhile to raise it here :)
I use asdf to manage go, among other things. The directory where I'm using m1-terraform-provider-helper isn't a go project, and I also don't have a global go version set. So even though m1-terraform-provider-helper's go dependency is satisfied via Homebrew, there's no go executable in my path. When I run any m1-terraform-provider-helper commands, it raises a panic because there's no GOPATH:
When I set an arbitrary go version or uninstall the asdf golang plugin entirely (so it falls back to /opt/homebrew/bin/go), the command runs as expected.
I can see that this has caused issues before, so even though this isn't a problem with m1-terraform-provider-helper per se, I'm wondering if it's possible to make the dependency more clear in the docs. Maybe something like what you wrote in the above-linked issue: "You need to have a go setup (because we use go to actually build the provider."
This isn't really a bug, but I found this behavior surprising and thought it might be worthwhile to raise it here :)
I use asdf to manage go, among other things. The directory where I'm using m1-terraform-provider-helper isn't a go project, and I also don't have a global go version set. So even though m1-terraform-provider-helper's go dependency is satisfied via Homebrew, there's no go executable in my path. When I run any m1-terraform-provider-helper commands, it raises a panic because there's no GOPATH:
When I set an arbitrary go version or uninstall the asdf golang plugin entirely (so it falls back to
/opt/homebrew/bin/go
), the command runs as expected.I can see that this has caused issues before, so even though this isn't a problem with m1-terraform-provider-helper per se, I'm wondering if it's possible to make the dependency more clear in the docs. Maybe something like what you wrote in the above-linked issue: "You need to have a go setup (because we use go to actually build the provider."
Your Environment