Skip to content

[ResponseOps][MW] Allow solutions to extend the scope of the MW #216718

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

Open
cnasikas opened this issue Apr 1, 2025 · 1 comment
Open

[ResponseOps][MW] Allow solutions to extend the scope of the MW #216718

cnasikas opened this issue Apr 1, 2025 · 1 comment
Labels
Feature:Maintenance Window Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@cnasikas
Copy link
Member

cnasikas commented Apr 1, 2025

The MW client and public APIs allow you to configure the scope of the MW. At the moment, the only supported scope where the MW is applied is the MW. We need to allow users to extend the scope of the MW with their own schema to be able to support applying the MW on their own workflows.

DoD

  • Create a backend MW registry where solutions define their scope schema.
  • The solution's scope schema will extend the scope schema of the MW public APIs.
  • The solution's scope schema will extend the scope schema of the MW client.
  • The MW client will persist and retrieve the solution's scope.
  • If a solution register a new scope or change an existing schema a test that the RO owns will fail. Solutions will need to update the test and the RO team will get pinged as code owners.
@cnasikas cnasikas added Feature:Maintenance Window Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Apr 1, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Maintenance Window Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

2 participants