Parse name and destination of the final executable

[Junkern]

Depending on the terraform provider the compiled binary can end up in different places with different names. This really depends on the Makefile and the resulting go install command.

What I have seen:

• $GOPATH/bin/: Most binaries end up here
• ~/.terraform.d/plugins: terraform-provider-datadog
• Inside the source code directory

Ideas:

• Parse the Makefile and look for indications about the final destination and name, e.g. go install -o test-provider
• As with Provide a way to do extra build steps (e.g. for hashicorp/aws) #1 have a map which has entries for special cases where the binary does not end up in $GOPATH/bin

[Junkern]

In the past year I have not seen one occurence of this problem => closing this issue.