-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Security Solution] - remove alerts subfeature UI from behind feature flag #108450
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
Conversation
|
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
peluja1012
left a comment
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!
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @yctercero |
| const ruleTypes = [ | ||
| SIGNALS_ID, | ||
| NOTIFICATIONS_ID, | ||
| ...(isRuleRegistryEnabled ? racRuleTypes : []), |
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.
Based on this remaining conditional on isRuleRegistryEnabled, even if the sub-feature privilege is shown, RAC rule types will not be included unless the feature flag is enabled.
Is this expected?
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.
Yes! That's expected. For 7.15 we are not shipping with rule registry rules.
… flag (elastic#108450) ### Summary This removes the feature flag check for showing the alerts subfeature under security solution Kibana roles UI.
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Summary
This removes the feature flag check for showing the alerts subfeature under security solution Kibana roles UI.