-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move PowerShell edge processing to ingest pipeline. #941
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
7c87383
to
7f8d15d
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
7f8d15d
to
2f159e0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Might want to move the change to the system changelog out of this PR.
I think we need to find a way to make the argument parsing stuff reusable, this looks more resilient than what I have in the Security pipeline.
2f159e0
to
16dec4c
Compare
Agreed. I think would be worth moving it to its own pipeline once this is done. |
* Move PowerShell edge processing to ingest pipeline. * Remove unrelated changelog fixes
* Move PowerShell edge processing to ingest pipeline. * Remove unrelated changelog fixes
What does this PR do?
Move PowerShell edge processing to ingest pipeline.
Checklist
changelog.yml
file.Relates to
Closes #905