-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Cases][Timeline] Saved Object Type Conversion #105677
Comments
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
In case anyone is following this issue but not the linked meta-issue (#100489): I published the Sharing Saved Objects developer guide, please take a look before proceeding with the implementation. And of course, please reach out if you run into any problems! |
Heads up, I'm adding a new reference to the Kibana data view saved object ( |
Chat today mapping the steps in the Sharing Saved Objects dev guide to each SO type:
@jonathan-buttner if you could take a look at the above and make sure I didn't miss anything, that would be great! feel free to just edit this comment if you need to add any links. |
@jportner yep that looks good 👍 |
Pinging @elastic/response-ops (Team:ResponseOps) |
As part of the effort to make saved objects shareable across multiple spaces we need to make a few changes to how Cases and Timeline interacts with the saved objects. This is required because in 8.0 the kibana core team is changing how the internal saved object id value is being stored to support being shared across multiple spaces.
The meta ticket for the core team is here: #100489.
The first thing is to migrate any of our foreign key fields (fields that reference another saved object's
id
field) to thereferences
field. After this migration is complete we need to switch our usage of the saved objectget
API to useresolve
instead as noted in the meta ticket above.The tasks associated with this work are the following:
.get
API to.resolve
and handle the 3 outcomes ([Cases][Sharable SOs] Use resolve for deep links #110854).resolve()
([Security Solution][Timeline][Sharable SOs] Use resolve for deep links #110862)The text was updated successfully, but these errors were encountered: