DeviceCode: Send engflow_auth
version in requests
#35
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.
This change modifies the HTTP client used by the
DeviceCode
Authenticator implementation to send version information in each request.The version info is sent in the
User-Agent
header, using the format:The version string is generated by the
buildstamp
library and is a semver string in a release binary, or a "pseudoversion" in a dev binary, similar go Go module pseudoversions.Tested:
bazel run //cmd/engflow_auth
against dev cluster fails (no buildstamp info)bazel run --stamp //cmd/engflow_auth
against dev cluster succeedsBug: linear/CUS-387