[Cloud Security] Fix cluster_id missing error in the Ingest Pipeline - #9434
Merged
Conversation
kfirpeled
approved these changes
Mar 24, 2024
maxcold
reviewed
Mar 25, 2024
💚 Build Succeeded
History
|
|
|
Package cloud_security_posture - 1.9.0-preview02 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
|
Package cloud_security_posture - 1.9.0 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
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
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.



Summary
This PR Fixes the Ingest Pipeline Error, this error was due to a missing check for the presence of the
cluster_idfield used in the copy_from.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Follow the guide described here to test this PR locally.
To collect the necessary data you can execute the following Reindex command in the dev tools (The pipeline is the important part!), point host and credentials to one of the long-running environments
Related issues