-
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][Exceptions] - Moves remaining exceptions builder logic into lists plugin #95266
Conversation
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Hi @yctercero we have looked in the ticket description and its on-going conversation and came up with some of the observation and Query . Build Details:
so can you please look into our observation if we are thinking in right direction and provide update on the queries raised for this ticket. Queries:
Observations:Please find below checkpoints checked from these changed done on 7.13.0-SNAPHOT having the latest commit changes. Found 01 Issue during testing: Please let us known if we are missing something or to validate anything more for this ticket. thanks !! |
The changes in bundle size don't need to be tested. In talking with Tyler it's clear that the lists plugin bundle size should be near 0 right now as the client side code is not needed on load. That is something that will need to be worked on. For this PR we are simply increasing the lists plugin and decreasing the security_solution plugin since we're just moving code from one to the other.
As part of the RAC initiative we are preparing these components to be used in any plugin that may need them and as such they need to be made more generic. The changes made in to the security solution were in line with this.
I pinged QA here because a file owned by QA is modified https://github.com/elastic/kibana/pull/95266/files#diff-0225f90a5daddb79c38b634443c805cf06cd83d05ebadc98c9d66883a1458049 so it needs QA code owners review. Because this work was chunked, it probably is best to wait for it all to be merged to 7.13 before testing it in 7.13. There should be no functionality changes to exceptions.
I checked that this issue does not occur in this PR. As you can see below, field suggestions appear as expected: |
thanks @yctercero for looking into out queries and providing feedback on them. However for the issue we will keep track this PR merge , will close issue if it get resolved . |
@elasticmachine merge upstream |
1 similar comment
@elasticmachine merge upstream |
I don't see any code changes that require @elastic/kibana-qa review. Is it still relevant? |
@dmlemeshko is relevant because without the review of the owner the PR cannot be merged. |
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 finally found removed test that is related to code coverage (owned by Kibana-QA).
@@ -35,14 +35,4 @@ describe(`enumeratePatterns`, () => { | |||
'src/plugins/charts/public/static/color_maps/color_maps.ts kibana-app' | |||
); | |||
}); | |||
it(`should resolve x-pack/plugins/security_solution/public/common/components/exceptions/builder/translations.ts to kibana-security`, () => { |
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.
Hey @dplumlee This test was "unlucky" to randomly select path that you changed. I think you just need to update it with one you have now and we are good. But please don't remove it completely
💛 Build succeeded, but was flaky
Test FailuresKibana Pipeline / general / sets and reads the url state for timeline by id.url state sets and reads the url state for timeline by idStack Trace
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @yctercero |
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
💔 Backport failed❌ 7.x: Commit could not be cherrypicked due to conflicts To backport manually run: |
…logic into lists plugin (elastic#95266) ## Summary Moves part of the exceptions UI out of the security solution plugin and into the lists plugin. In order to keep PRs (relatively) small, I am moving single components at a time. This should also then help more easily pinpoint the source of any issues that come up along the way. The next couple PRs will focus on the exception builder. This one in particular is focused on moving over the `ExceptionBuilderComponent` which deals with rendering numerous exception items and their entries. Quick Summary: - `x-pack/plugins/security_solution/public/common/components/exceptions/builder/` → ` x-pack/plugins/lists/public/exceptions/components/builder/` - Corresponding unit test file moved as well - Updated security solution exception builder to pull `ExceptionBuilderComponent` from lists plugin # Conflicts: # packages/kbn-optimizer/limits.yml # src/dev/code_coverage/ingest_coverage/__tests__/enumerate_patterns.test.js
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
1 similar comment
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
…ilder logic into lists plugin (#95266) (#96358) * [Security Solution][Exceptions] - Moves remaining exceptions builder logic into lists plugin (#95266) ## Summary Moves part of the exceptions UI out of the security solution plugin and into the lists plugin. In order to keep PRs (relatively) small, I am moving single components at a time. This should also then help more easily pinpoint the source of any issues that come up along the way. The next couple PRs will focus on the exception builder. This one in particular is focused on moving over the `ExceptionBuilderComponent` which deals with rendering numerous exception items and their entries. Quick Summary: - `x-pack/plugins/security_solution/public/common/components/exceptions/builder/` → ` x-pack/plugins/lists/public/exceptions/components/builder/` - Corresponding unit test file moved as well - Updated security solution exception builder to pull `ExceptionBuilderComponent` from lists plugin # Conflicts: # packages/kbn-optimizer/limits.yml # src/dev/code_coverage/ingest_coverage/__tests__/enumerate_patterns.test.js * removing file that exists in master but not backported to 7.x mistakenly included in backport upon cherry picking Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
Moves part of the exceptions UI out of the security solution plugin and into the lists plugin. In order to keep PRs (relatively) small, I am moving single components at a time. This should also then help more easily pinpoint the source of any issues that come up along the way.
The next couple PRs will focus on the exception builder. This one in particular is focused on moving over the
ExceptionBuilderComponent
which deals with rendering numerous exception items and their entries.Quick Summary:
x-pack/plugins/security_solution/public/common/components/exceptions/builder/
→x-pack/plugins/lists/public/exceptions/components/builder/
ExceptionBuilderComponent
from lists pluginEntry Item (PR)
Exception Item (PR)
Builder (THIS PR DEALS WITH 👇🏽)
Builder Buttons (THIS PR DEALS WITH 👇🏽)
Exception Item Comments
Builder Modal
Notes
Testing
Prior to making these changes, added a number of tests to ensure coverage of existing functionality. For manual testing, please checkout PR and play around with the following:
or
operator)Checklist