[8.19](backport #44891) Exclude Azure VM provider in add_cloud_metadata processor in FIPS builds
#44910
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
…uilds (#44891) * Exclude Azure provider in add_cloud_metadata processor in FIPS builds * Add warning to doc * Adding CHANGELOG entry * Updating PR number in CHANGELOG entry * Clarify provider in CHANGELOG entry * Do not compile Azure provider code * Do not compile Azure provider tests * Remove CHANGELOG entries (cherry picked from commit 383a4c6)
botelastic
bot
added
the
needs_team
|
This pull request doesn't have a |
Kavindu-Dodan
approved these changes
Jun 19, 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
This PR amends the
add_cloud_metadataprocessor initialization such that the Azure Virtual Machine provider is included only in non-FIPS builds.The Azure Virtual Machine provider depends on the Azure SDK which, in turn, depends on the golang.org/x/crypto/pkcs12 package, which is not FIPS-compliant, and the SDK doesn't plan to offer a way to disable the use of this package at compile time (see Azure/azure-sdk-for-go#24336).
Checklist
I have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
The
add_cloud_metadataprocessor will not support the Azure Virtual Machine provider in FIPS-capable artifacts of Beats.This is an automatic backport of pull request #44891 done by [Mergify](https://mergify.com).