[Entity Analytics] Split out asset criticality routes and constants into their own files #180531
Assignees
Labels
Team:Entity Analytics
Security Entity Analytics Team
technical debt
Improvement of the software architecture and operational architecture
Comments
hop-dev
added
technical debt
|
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
hop-dev
added a commit
that referenced
this issue
Apr 15, 2024
…e entity analytics team (#180702) ## Summary Closes #180531 This pull request moves entity analytics route registration and url definition into files owned by our team. Currently, to add a new route we require a code owners review from both the `security-detections-response` and `security-threat-hunting` teams unnecessarily. This is because we needed to change the following files: - `x-pack/plugins/security_solution/common/constants.ts` - `x-pack/plugins/security_solution/server/routes/index.ts` As recommended by @maximpn [here](#179930 (review)) I have also removed redundant feature flag checks for enabling risk scoring and risk engine privileges routes, these feature flags are enabled now. --------- Co-authored-by: Kibana Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement the recommended changes from #179930 (review) so that we own more code!
The text was updated successfully, but these errors were encountered: