[Security Solution][Investigations][Tech Debt] - Timeline Data Reducers

[michaelolo24]

Background:

We currently use the concept of containers (custom hooks that fetch data) within the security solution to allow data to be fetched and consumed from any component within the application. While this allows for a lot of flexibility, moving this data to a shared reducer would allow other parts of the application to react based on the existing data as well as unify on the one way data flow through redux to make it easier to reason about the application.

Details:

Reducers should be created to match state for each of the data sources below. Actions can then be created to fire off the api requests via middleware with any configurable fields and then stored in the reducer to be fetched via selectors across the application.

The containers for the timelines plugin are all located:

x-pack/plugins/security_solution/public/timelines/containers

• /all
• /details
• /kpis
• /local_storage
• /notes
• /pinned_events
• api.ts
• index.tsx

x-pack/plugins/timelines/container

• /source
• index
• use_update_alerts

Acceptance Criteria:

• Cypress Tests are added for any UI changes (https://docs.cypress.io/guides/guides/network-requests)
  • For all the referenced API's in
    • security_solution: all/, details/, kpis/, local_storage/, notes/, pinned_events/, api.ts, index.tsx
    • timelines: source/, index.tsx, use_update_alerts:
    • Add fixtures of successful API responses
    • Add fixtures for failed API responses
    • Test actions launched lead to the expected success and failure scenarios
    • Test calls are only made the correct # of times
• Functional Tests are added for any server changes
• Untested code paths should have unit tests added
• The application functions as before

[elasticmachine]

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

[michaelolo24]

Closing in favor of: #124138