Closed efd6 closed 1 month ago
This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @efd6? 🙏. For such, you'll need to label your PR with:
To fixup this pull request, you need to add the backport labels for the needed branches, such as:
backport-8./d
is the label to automatically backport to the 8./d
branch. /d
is the digitbackport-8.x
has been added to help with the transition to the new branch 8.x
.
If you don't need it please use backport-skip
label and remove the backport-8.x
label.
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)
This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/
git fetch upstream
git checkout -b i10744-awss3 upstream/i10744-awss3
git merge upstream/main
git push upstream i10744-awss3
This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/
git fetch upstream
git checkout -b i10744-awss3 upstream/i10744-awss3
git merge upstream/main
git push upstream i10744-awss3
Proposed commit message
The test file txn.csv.gz was obtained from https://netskopepartnerlogfilebucket.s3.amazonaws.com/txn-1722875066329034-fe10b6a23cc643c4b282e6190de2352d.csv.gz
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs