Open xcrzx opened 3 weeks ago
Pinging @elastic/security-solution (Team: SecuritySolution)
Pinging @elastic/security-detections-response (Team:Detections and Resp)
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)
Summary
Currently, we have the rule schema defined in multiple places and contexts, such as rule response, diffable rule, rule upgrade specifiers, etc. This fragmented approach leads to a sub-optimal developer experience and is prone to errors. When a new rule field is added, developers must manually update all locations where rule schemas are defined, which is time-consuming and error-prone.
Proposal:
Explore the possibility of creating a single source of truth for rule schemas.
Key Points:
Single Configuration File:
Code Generation:
Verify that the approach allows us to achieve