o365: validate field type in pipeline before accessing subfields #14056
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
chemamartinez added Integration:o365 
| Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
efd6 approved these changes May 29, 2025
Contributor
| Though it would be nice to have a test for this. |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
| Package o365 - 2.17.1 containing this change is available at https://epr.elastic.co/package/o365/2.17.1/ |
anupratharamachandran pushed a commit to anupratharamachandran/integrations that referenced this pull request Jun 2, 2025
…stic#14056) As organization field may be a string instead of an object, the following error can appear when accessing its subfields being a string value. Processor 'conditional' with tag '' failed with message 'dynamic getter [java.lang.String, id] not found' Added a type check before accessing its subfields to avoid the error above.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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
As
organizationfield may be a string instead of an object, the following error can appear when accessing its subfields being a string value.Added a type check before accessing its subfields to avoid the above error.
Checklist
changelog.ymlfile.