-
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] Remove references to ruleRegistryEnabled feature flag #128913
Conversation
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
@elasticmachine merge upstream |
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.
Cases code LTGM
@elasticmachine merge upstream |
@@ -190,7 +181,7 @@ export const importRules = async ({ | |||
language, | |||
license, | |||
machineLearningJobId, | |||
outputIndex: signalsIndex, | |||
outputIndex: '', |
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.
This field is deprecated, no? We just need to remove it at some point, right?
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.
@spong Yep, good point. We left it because the feature flag was still there and so it may have still been needed. I can follow up to remove it!
throw new PrepackagedRulesError( | ||
`Pre-packaged rules cannot be installed until the signals index is created: ${signalsIndex}`, | ||
400 | ||
); |
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.
Is this error still possible even with the RuleRegistry? Like if you create a new space, but don't go to the security app, and then hit this API directly the indices won't have been created yet, no? RuleRegistry index creation happens on Kibana startup for existing spaces, but new spaces require an alert to be generated, is that correct?
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.
@spong I'll have to test this scenario, but you may be right. I think I'll follow up with an additional PR/issue to address this and the output_index
stuff.
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.
Did a quick scan over code changes and LGTM! Couple questions around test changes, but everything else looks good -- thanks for all the cleanup here @madirey! 🙂 🙌 🚀
@elasticmachine merge upstream |
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.
Thanks for removing the flags! LGTM
💛 Build succeeded, but was flakyTest Failures
Metrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
…flag (elastic#128913) * Remove references to ruleRegistryEnabled feature flag * Fix remaining tests using describe.each * Test fixes * alert -> rule * Fix import rule tests * Fix output_index in tests * Tryin' again * Another test fix Co-authored-by: Kibana Machine <[email protected]>
Summary
Since
rule_registry
is now enabled by default, legacy rule executors have now been disabled. This removes all references to the feature flag in areas where legacy code was running or legacy alerts were written.Fixes #128918
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers