o365: Support non-array Parameters and ExtendedProperties fields #26164
Conversation
This file contains 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
These fields are documented as being an array of Name-value pairs. However, in some cases they appear as a string field, leading to mapping errors. This patch will perform the expected name-value conversion by creating a new key, "_raw" with the original field value, when the fields are not arrays.
adriansr
added
bug
review
Team:Security-External Integrations
backport-v7.13.0
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
botelastic
bot
added
needs_team
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
mergify bot
pushed a commit
that referenced
this pull request
Jun 7, 2021
) These fields are documented as being an array of Name-value pairs. However, in some cases they appear as a string field, leading to mapping errors. This patch will perform the expected name-value conversion by creating a new key, "_raw" with the original field value, when the fields are not arrays. (cherry picked from commit 07fa7f6)
mergify bot
pushed a commit
that referenced
this pull request
Jun 7, 2021
) These fields are documented as being an array of Name-value pairs. However, in some cases they appear as a string field, leading to mapping errors. This patch will perform the expected name-value conversion by creating a new key, "_raw" with the original field value, when the fields are not arrays. (cherry picked from commit 07fa7f6)
adriansr
pushed a commit
that referenced
this pull request
Jun 9, 2021
…dProperties fields (#26169) These fields are documented as being an array of Name-value pairs. However, in some cases they appear as a string field, leading to mapping errors. This patch will perform the expected name-value conversion by creating a new key, "_raw" with the original field value, when the fields are not arrays. (cherry picked from commit 07fa7f6)
adriansr
pushed a commit
that referenced
this pull request
Jun 9, 2021
…edProperties fields (#26170) These fields are documented as being an array of Name-value pairs. However, in some cases they appear as a string field, leading to mapping errors. This patch will perform the expected name-value conversion by creating a new key, "_raw" with the original field value, when the fields are not arrays. (cherry picked from commit 07fa7f6)
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.
These fields are documented as being an array of Name-value pairs. However, in some cases they appear as a string field, leading to mapping errors.
This patch will perform the expected name-value conversion by creating a new key,
_rawwith the original field value, when the fields are not arrays.