Skip to content

amazon_security_lake: remove incoming null fields - #14392

Merged
efd6 merged 1 commit into
elastic:mainfrom
efd6:s6140-amazon_security_lake
Jul 2, 2025
Merged

amazon_security_lake: remove incoming null fields#14392
efd6 merged 1 commit into
elastic:mainfrom
efd6:s6140-amazon_security_lake

Conversation

@efd6

@efd6 efd6 commented Jul 2, 2025

Copy link
Copy Markdown
Contributor

Proposed commit message

amazon_security_lake: remove incoming null fields

It seems that the conventional approach to tesing for the presence of fields is
inadequately safe; if a field is null but present, the test over optimistically
allows potentially sensitive processors, such as rename, to fail. So remove all
null fields on entry.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 self-assigned this Jul 2, 2025
@efd6 efd6 added bugfix Pull request that fixes a bug issue Integration:amazon_security_lake Amazon Security Lake Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Jul 2, 2025
It seems that the conventional approach to tesing for the presence of fields is
inadequately safe; if a field is null but present, the test over optimistically
allows potentially sensitive processors, such as rename, to fail. So remove all
null fields on entry.
@efd6
efd6 force-pushed the s6140-amazon_security_lake branch from d573158 to da66670 Compare July 2, 2025 07:10
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

cc @efd6

@efd6
efd6 marked this pull request as ready for review July 2, 2025 07:56
@efd6
efd6 requested a review from a team as a code owner July 2, 2025 07:56
@elasticmachine

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6
efd6 requested a review from ShourieG July 2, 2025 07:56

@ShourieG ShourieG left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@efd6
efd6 merged commit 758ecfe into elastic:main Jul 2, 2025
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package amazon_security_lake - 2.5.3 containing this change is available at https://epr.elastic.co/package/amazon_security_lake/2.5.3/

robester0403 pushed a commit to robester0403/integrations that referenced this pull request Jul 8, 2025
It seems that the conventional approach to tesing for the presence of fields is
inadequately safe; if a field is null but present, the test over optimistically
allows potentially sensitive processors, such as rename, to fail. So remove all
null fields on entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Pull request that fixes a bug issue Integration:amazon_security_lake Amazon Security Lake Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

3 participants