fix: embed troubleshoot version string from module dependency #1371
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description, Motivation and Context
If troubleshoot is used as a dependency (part of your
go.mod
), the version information of the release would be missing at runtime i.e empty string whenversion.Version()
is called. This is because the version string is injected to binaries at build time using linker flags (LD) passed to the compiler. Built binaries such assupport-bundle
andpreflight
will contain a version string, but projects such as KOTS that import troubleshoot as a module will not have a version string set.This PR utilises information fetched from
runtime.BuildInfo
at runtime to extract the version info from the troubleshoot module in thego.mod
file.Fixes: #1372
Checklist
Does this PR introduce a breaking change?