-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[SecuritySolution] Revamp entity analytics Open API schemas #182666
Conversation
/ci |
/ci |
/ci |
...k/plugins/security_solution/public/entity_analytics/components/risk_score_enable_section.tsx
Show resolved
Hide resolved
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
/ci |
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.
Threat hunting explore 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.
Love it! 🚀
I think I prefer using the RiskEngineStatusEnum type
instead of RiskEngineStatus.enum
but its completely a matter of opinion so not blocking this from being merged 👍
x-pack/plugins/security_solution/common/entity_analytics/risk_engine/risk_levels.ts
Outdated
Show resolved
Hide resolved
...k/plugins/security_solution/common/search_strategy/security_solution/risk_score/all/index.ts
Outdated
Show resolved
Hide resolved
.../security_solution/public/entity_analytics/api/hooks/use_calculate_entity_risk_score.test.ts
Outdated
Show resolved
Hide resolved
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 for the Threat Hunting Investigations team!
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.
@machadoum thank you for addressing Entity Analytics OAS issues and making them better 🙏
There is no public API endpoint here so there is no immediate impact on Serverless API documentation effort. But it's good to have ready to use OAS when we need them. Rule Management team have work related to UI and test clients generation in the backlog. AS part of this task bundling public and internal OAS will be necessary.
I tested revamped OAS files with @kbn/openapi-bundler
and didn't find any issues.
While I didn't review all the changes I left a few comments I found on discrepancies.
...ity_solution/common/api/entity_analytics/asset_criticality/get_asset_criticality.schema.yaml
Outdated
Show resolved
Hide resolved
...k/plugins/security_solution/common/api/entity_analytics/asset_criticality/common.schema.yaml
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/common/api/entity_analytics/common/common.schema.yaml
Outdated
Show resolved
Hide resolved
* Rename EntityRiskScore type * Use enum type when possible * Update yaml to use sinigle quote * Rename EntityRiskScore to EntityRiskScoreRecord
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: cc @machadoum |
Summary
buildRouteValidationWithZod
x-pack/plugins/security_solution/common/api/entity_analytics/risk_engine/common.schema.yaml
. There were 2 common files.yaml
files for consistency.yaml
files from{name}_schema.yml
to{name}.schema.yml
. Otherwise, they don't work with the generator.RiskScore
toEntityRiskScoreRecord
(requested by Maxim)