## Summary
Holy moly.
What is happening in this PR? 🤷🏽♀️ Let's break it down:
- Added a package `@kbn/alerts` - another one?! ...yes
- This is meant to add shared hooks and components around alerts as data
- `useGetUserAlertsPermissions` - accepts the Kibana capabilities object and returns whether the user has `read` and `crud` alerts privileges
- `AlertsFeatureNoPermissions` - component displayed when user does not have alerts privileges
- UI changes for user with NO alerts privileges
- `Alerts` tab hidden in security solution side navigation
- `Alerts` tab hidden in rule details page
- UI changes for user with alerts READ ONLY privileges
- alerts checkboxes hidden in alerts table
- alerts bulk actions hidden in alerts table
Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com>
10 lines
279 B
JSON
10 lines
279 B
JSON
{
|
|
"name": "@kbn/alerts",
|
|
"version": "1.0.0",
|
|
"description": "Alerts components and hooks",
|
|
"license": "SSPL-1.0 OR Elastic License 2.0",
|
|
"browser": "./target_web/index.js",
|
|
"main": "./target_node/index.js",
|
|
"types": "./target_types/index.d.ts",
|
|
"private": true
|
|
}
|