-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Security Solution][Sourcerer] Colocate sourcerer files #184149
Conversation
381de18
to
8a8b774
Compare
8a8b774
to
3f81092
Compare
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations) |
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.
Entity analytics changes LGTM!
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.
session_viewer
and kubernetes
changes lgtm!
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.
Only imports have been changed in the Rules Management area. LGTM
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
Summary
TLDR; Even though many files are changed here, its only about sorting out the imports and file locations.
Moving sourcerer to a single directory, to keep entire feature implmentation close - in an effort to draw clear boundaries over its api, imports and exports - similar to how
security flyout
is implemented.This is a starting point towards refactoring the component to use discover picker and apis.