Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Task Manager] [8.0] Add migrations for "actions:* and "alerting:*" task types #108084

Closed
chrisronline opened this issue Aug 10, 2021 · 1 comment · Fixed by #109180
Closed

[Task Manager] [8.0] Add migrations for "actions:* and "alerting:*" task types #108084

chrisronline opened this issue Aug 10, 2021 · 1 comment · Fixed by #109180
Assignees
@YulNaumenko
Labels
estimate:small Small Estimated Level of Effort Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) technical debt Improvement of the software architecture and operational architecture

Comments

@chrisronline
Copy link
Contributor

Relates to #100067

Starting in 8.0, we need to ensure that the task manager task documents are updated to point to the new, migrated saved object IDs for actions and alerting task types. This is only applicable for saved objects that live in a custom space - saved objects in the default space are not affected. Both task types contain a spaceId param that will tell us this.

Alerting task types contain an alertId params that needs to be migrated from a legacy ID to a migrated saved object ID using this newly added API.

Action task types contain an actionTaskParamsId params that needs to be migrated from a legacy ID to a migrated saved object ID using this newly added API.

See the PoC PR for more insight into how this might work.
@chrisronline chrisronline added loe:medium Medium Level of Effort Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Aug 10, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@chrisronline chrisronline mentioned this issue Aug 10, 2021
Closed
@gmmorris gmmorris added Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework technical debt Improvement of the software architecture and operational architecture labels Aug 13, 2021
@YulNaumenko YulNaumenko self-assigned this Aug 16, 2021
@gmmorris gmmorris added the estimate:small Small Estimated Level of Effort label Aug 18, 2021
@YulNaumenko YulNaumenko mentioned this issue Aug 18, 2021
Merged
1 task
@gmmorris gmmorris added estimate:small Small Estimated Level of Effort and removed estimate:small Small Estimated Level of Effort labels Aug 19, 2021
@YulNaumenko YulNaumenko mentioned this issue Aug 27, 2021
Merged
1 task
@gmmorris gmmorris removed the loe:medium Medium Level of Effort label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YulNaumenko YulNaumenko

Labels
estimate:small Small Estimated Level of Effort Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Milestone
No milestone
5 participants
@chrisronline @gmmorris @kobelb @elasticmachine @YulNaumenko