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.

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

Import and export Cases using saved-object management #82533

Closed
kobelb opened this issue Nov 3, 2020 · 5 comments · Fixed by #110148
Closed

Import and export Cases using saved-object management #82533

kobelb opened this issue Nov 3, 2020 · 5 comments · Fixed by #110148
Assignees
Labels
Feature:Cases Cases feature Project:RemoveLegacyMultitenancy Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM Team:Threat Hunting Security Solution Threat Hunting Team

Comments

@kobelb
Copy link
Contributor

kobelb commented Nov 3, 2020

End-users will commonly use saved-object management's import/export functionality to move saved-objects from one instance to another. Cases should be included in these exports, so end-users have an easy way to migrate all of their saved-objects in a unified manner.

As part of the effort to remove legacy multi-tenancy, we want to give our users a way to migrate from a legacy tenant to Spaces. Without the ability to import/export Cases, if a user is using a legacy tenant, their data will be stuck in that tenant and they won't have a migration path for 8.0.

As far as I'm aware, there is currently blocked by #82064

@kobelb kobelb added Project:RemoveLegacyMultitenancy Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM labels Nov 3, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

@kobelb kobelb added the Feature:Cases Cases feature label Nov 3, 2020
@kobelb
Copy link
Contributor Author

kobelb commented Feb 22, 2021

The ability to export hidden saved-objects and specify onExport hooks has been addressed, so this should no longer be blocked.

If you do happen to find some other infrastructure that is required to make cases importable/exportable, please let us know in #82020.

@rudolf
Copy link
Contributor

rudolf commented Sep 7, 2021

Looks like this will be closed in #110148

@cnasikas
Copy link
Member

cnasikas commented Sep 7, 2021

cc @jonathan-buttner

@jonathan-buttner jonathan-buttner added the Team:Threat Hunting Security Solution Threat Hunting Team label Sep 7, 2021
@elasticmachine
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Cases Cases feature Project:RemoveLegacyMultitenancy Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM Team:Threat Hunting Security Solution Threat Hunting Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants