Skip to content
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

Merged

Conversation

nikitaindik
Copy link
Contributor

Partially addresses: #184364

Summary

As a first step in refactoring our newly added rulesManagementClient, we are renaming it from rulesManagementClient to detectionRulesClient.

rulesManagementClient looks and sounds too similar to a long existing rulesClient, 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.

@nikitaindik nikitaindik added refactoring release_note:skip Skip the PR/issue when compiling release notes backport:skip This commit does not require backporting Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Feature:Rule Management Security Solution Detection Rule Management area Team:Detection Rule Management Security Detection Rule Management Team v8.15.0 labels May 31, 2024
@nikitaindik nikitaindik self-assigned this May 31, 2024
@nikitaindik nikitaindik requested review from a team as code owners May 31, 2024 15:53
@nikitaindik nikitaindik requested a review from rylnd May 31, 2024 15:53
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@nikitaindik nikitaindik requested a review from dplumlee May 31, 2024 15:53
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@banderror banderror requested review from e40pud and yctercero and removed request for rylnd May 31, 2024 16:18
Copy link
Contributor

@banderror banderror left a 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 👍

Copy link
Contributor

@yctercero yctercero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rename LGTM!

Copy link
Contributor

@e40pud e40pud left a 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

@nikitaindik nikitaindik enabled auto-merge (squash) June 3, 2024 09:00
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @nikitaindik

@nikitaindik nikitaindik merged commit 10f6174 into elastic:main Jun 3, 2024
35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:Rule Management Security Solution Detection Rule Management area refactoring release_note:skip Skip the PR/issue when compiling release notes Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.15.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants