-
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] Rename rulesManagementClient
-> detectionRulesClient
#184598
[Security Solution] Rename rulesManagementClient
-> detectionRulesClient
#184598
Conversation
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management) |
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 is a good name improvement! Thanks for carefully renaming it everywhere @nikitaindik, LGTM 👍
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.
Rename LGTM!
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 the update! LGTM
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @nikitaindik |
Partially addresses: #184364
Summary
As a first step in refactoring our newly added
rulesManagementClient
, we are renaming it fromrulesManagementClient
todetectionRulesClient
.rulesManagementClient
looks and sounds too similar to a long existingrulesClient
, so it can be confusing to new devs or anyone quickly digging through the code.This PR just updates the name. Other refactorings will be arriving in the upcoming PRs.