-
Notifications
You must be signed in to change notification settings - Fork 22
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
Report correct version #66
Comments
Thanks for this. In the meantime we could use a similar approach to tfexec: the version.go file is modified during release (https://github.com/hashicorp/terraform-exec/blob/main/scripts/release/release.sh#L60). |
For the If we decide to distribute our own binaries then we'd still have to use the approach you mentioned, or I personally like the idea of dependency/wrapper-free build process, so I'd be leaning more towards the Here's a full context helpfully explained by Martin in another PR as he ran into the exact same problem I did
|
btw. we don't even need the vcs revision which was added in Go 1.18. We can just use the |
Same issue for terraform-exec (opened while we were still building tfinstall binaries): hashicorp/terraform-exec#22 Another problem with debug.BuildInfo is golang/go#33976. |
That seems annoying. I missed that one entirely - good catch! @tgross also mentioned that Nomad would welcome if installing In other words, we should make sure that these binaries we build are also distributed as Linux packages and via our Homebrew tap too, so that users don't end up re-implementing the integrity checking in shell or avoid checking altogether. |
Currently we report old version in both the CLI and User-Agent as it's hard-coded here:
hc-install/internal/version/version.go
Lines 1 to 9 in c241e27
We can explore https://pkg.go.dev/debug/buildinfo or ldflags for the CLI.
The text was updated successfully, but these errors were encountered: