-
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
[Alerting] [8.0] Prepare for making alerting saved objects sharecapable #107084
Labels
enhancement
New value added to drive a business result
estimate:small
Small Estimated Level of Effort
Feature:Alerting/RulesFramework
Issues related to the Alerting Rules Framework
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
It would be nice to add a functional test that mimics the verification steps from this PR. Perhaps use |
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New value added to drive a business result
estimate:small
Small Estimated Level of Effort
Feature:Alerting/RulesFramework
Issues related to the Alerting Rules Framework
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Related to #107069
To prepare for shareable saved objects in 8.0, we need to make two changes that can only go into 8.0:
namespaceType: 'multiple-isolated'
(instead ofnamespaceType: 'single'
)Because we are able to get the current Kibana version from core, we might be able to create a single set of backportable changes that work in both environments. If this is not feasible, this change can only go into master.
See the PoC PR for more insight into how this might work.
The text was updated successfully, but these errors were encountered: