-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Security Solution][Alerts] Add tests for changes in the schema #110798
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
Team: SecuritySolutionSecurity Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Team:Detection EngineSecurity Solution Detection Engine AreaSecurity Solution Detection Engine AreaTeam:Detections and RespSecurity Detection Response TeamSecurity Detection Response TeamTheme: raclabel obsoletelabel obsoletetechnical debtImprovement of the software architecture and operational architectureImprovement of the software architecture and operational architecture
Metadata
Metadata
Assignees
Labels
Team: SecuritySolutionSecurity Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Team:Detection EngineSecurity Solution Detection Engine AreaSecurity Solution Detection Engine AreaTeam:Detections and RespSecurity Detection Response TeamSecurity Detection Response TeamTheme: raclabel obsoletelabel obsoletetechnical debtImprovement of the software architecture and operational architectureImprovement of the software architecture and operational architecture
Type
Fields
Give feedbackNo fields configured for issues without a type.
Parent ticket: #101016
Related to: #109293
Summary
(Immediately after 7.15.0)
Add tests that compare the 7.15 shipped schema to the 7.16+ schema in development to ensure that the existing schema can be upgraded properly.
Ideas:
ruleDataService.initializeIndex())Background
The background for this is our discussions with @kobelb (see #109276 (comment) and above comments) on the "compatibility" of the current index upgrade logic with the ideas for backwards compatibility (#109293).