Martin
Martin
Okay, thanks. That was very helpful! I will provide a fix in a few hours!
@nishant-ci Should be fixed with version `0.5.1`. Thanks for reporting!
I have never worked with terraform cloud, so I would be interested in those changes. Are those changes something `m1-terraform-provider-helper` should do out of the box? Or with a flag?
Hmmm, interesting. Thanks for the explanation! This could make for a good addition to the tool, but I will have to think things through first.
@nishant-ci I just released `v0.7.0` which has a `m1-terraform-provider-helper lockfile upgrade` command to add the hashes of the local providers to the lockfile. Does that help with your problem?
Please supply the `-v` flag to supply a value As shown in the README ``` m1-terraform-provider-helper activate # (In case you have not activated the helper) m1-terraform-provider-helper install hashicorp/vault -v...
Closing, as the initial problem was fixed.
This is probably because the `opsgenie` provider is using `goreleaser` in their `make build` and that places the files somewhere unexpected. @GustavJaner could you open a seperate issue for that?
Thanks for the PR. Are you having issues installing AWS provider? For me this is working: `m1-terraform-provider-helper install hashicorp/aws -v v2.70.0 ` I am running on `go version go1.17.6 darwin/arm64`
@et304383 sorry for the long delay. I am actually torn between the two decisions... on the one hand it is not a problem of this tool, but of the provider...