-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Create new host flyout #173392
Conversation
a41c98c
to
c778935
Compare
e52e022
to
fb2ad7c
Compare
* Refactor user flyout components to be reused by hosts
fcc3e4b
to
32a45ba
Compare
x-pack/plugins/security_solution/public/flyout/entity_details/host_right/content.tsx
Outdated
Show resolved
Hide resolved
85a8b6b
to
b993b8a
Compare
b993b8a
to
5d29c5d
Compare
Adapt risk summary to both entity flyouts
5849ca8
to
3337336
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.
LGTM for the Threat Hunting Investigations team
1aa2bca
to
6bed3c0
Compare
...ns/security_solution/public/entity_analytics/components/risk_summary_flyout/risk_summary.tsx
Outdated
Show resolved
Hide resolved
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.
Explore code LGTM
@elasticmachine merge upstream |
.../security_solution/public/flyout/entity_details/host_right/fields/endpoint_policy_fields.tsx
Outdated
Show resolved
Hide resolved
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.
LGTM, other than some minor nits
But since I worked on this feature, someone else from @elastic/security-entity-analytics should also take a look for final approval
.../security_solution/public/flyout/entity_details/host_right/hooks/use_observed_host_fields.ts
Outdated
Show resolved
Hide resolved
[mlCapabilities] | ||
); | ||
|
||
if (!hostData.details) return []; |
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.
NIT: I've been constantly reminded in reviews that standard practice is to never return
without braces in if
checks 😆
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.
Sergi also asked me to fix that. I am updating it everywhere. But I think it is weird that we have a code style preference that isn't included in the code style CI check (prettier).
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.
I agree we should either have a lint rule for this or not care, I quite like it without the braces 😅
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.
Yeah, I definitely agree, I asked the same, about having a lint rule.
I much prefer it without the braces, but if it's standard practice, we should have rule because I will definitely keep forgetting about it
x-pack/plugins/security_solution/public/flyout/entity_details/mocks/index.ts
Show resolved
Hide resolved
...ns/security_solution/public/flyout/entity_details/shared/components/entity_table/columns.tsx
Outdated
Show resolved
Hide resolved
...plugins/security_solution/public/flyout/entity_details/user_right/hooks/use_observed_user.ts
Outdated
Show resolved
Hide resolved
...s/security_solution/public/flyout/entity_details/user_right/hooks/use_observed_user_items.ts
Outdated
Show resolved
Hide resolved
.../plugins/security_solution/public/timelines/components/timeline/body/renderers/host_name.tsx
Outdated
Show resolved
Hide resolved
.../security_solution/public/flyout/entity_details/host_right/hooks/use_observed_host_fields.ts
Outdated
Show resolved
Hide resolved
ES returns formatted strings by default.
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
## Summary issue: #173392 Flaky test runner runs: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4773 https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4841 * Add cypress test to the new User and Host flyouts. * Fix function using the wrong host risk score index * Fix some cypress flakiness ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Kibana Machine <[email protected]>
## Summary issue: elastic#173392 Flaky test runner runs: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4773 https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4841 * Add cypress test to the new User and Host flyouts. * Fix function using the wrong host risk score index * Fix some cypress flakiness ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Kibana Machine <[email protected]>
Summary
Create the Expandable Host flyout with the risk inputs panel.
What is included
What is not included
How to test it?
newHostDetailsFlyout
host.name
fieldhost.name
field