-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SecuritySolution] Fix schedule risk engine callout when engine is in…
…stalled but disabled (#196496) ## Summary Fix the visibility of the Schedule Risk Engine Callout inside the asset criticality bulk upload when the risk engine is disabled. The callout should not be displayed when the risk engine is installed but disabled. ### How to test it? * Open Kibana - Security Solution * Navigate to the risk engine page and install the risk engine * On the same page, disable the risk engine * Navigate to the asset criticality page * Successfully upload a document * You should see a "success" but no risk engine callout. ![Screenshot 2024-10-16 at 10 41 39](https://github.com/user-attachments/assets/5c8f078e-4588-434e-8c76-03d72b1c5a16) ### Checklist - [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 (cherry picked from commit 1de6fb5)
- Loading branch information
Showing
2 changed files
with
27 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters