[8.19](backport #44865) [FIPS] Disable Microsoft Go telemetry #44896
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* [FIPS] Disable Microsoft Go telemetry * Add CHANGELOG entry * Remove check for MS_GOTOOLCHAIN_TELEMETRY_ENABLED from package. That env var affects the behavior of the Go toolchain at build time, not the behavior of the Beats binaries at runtime. (cherry picked from commit b9ce100)
mergify
bot
requested review from
belimawr and
leehinman
and removed request for
a team
botelastic
bot
added
the
needs_team
github-actions
bot
added
the
Team:Elastic-Agent-Data-Plane
botelastic
bot
removed
the
needs_team
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
ycombinator
approved these changes
Jun 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed commit message
Disables sending telemetry to Microsoft when using their Go fork for producing FIPS-capable build artifacts.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
None; FIPS-capable artifacts have not been released yet.
Author's Checklist
This is an automatic backport of pull request #44865 done by [Mergify](https://mergify.com).