fix AWS Lambda message handling#19250
Draft
Kavindu-Dodan wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
a32f83b to
0277758
Compare
💚 Build Succeeded
|
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.
Proposed commit message
aws.lambda.messageis defined as aflattenedfield. However, Lambda log's JSON pipeline ignore checks to validate this. This cause JSON pipeline to parse but indexing to fail.If the payload contains a non-compliant content, then this fix preserve the original message at root level
messagefield.Checklist
changelog.ymlfile.