Server side saved objects import / export API #27203
Labels
enhancement
New value added to drive a business result
Meta
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
We will use this meta issue to track the proposed plan for server side import / export API. The main goals are to allow saved objects to automatically export their own dependencies and to allow import / export on any type of saved object.
Once complete, this should resolve the following issues:
Once complete, this should facilitate the following issues:
Phases
The completion of saved objects import / export API will be implemented in the following phases.
Phase 1 - Create saved object relationships#27210
In this phase, we need to layout the groundwork for the enhancements we want to do to the import / export feature. In order to have automatic conflict discovery and automatic dependency exporting, we need to store at a generic level what each saved object has references to.
Phase 2 - Write a server side API for import / export#4759
In this phase, we need to move existing functionality to the server side. We will also order the objects on export so the import API doesn't have to worry about the dependencies not being declared first. The import API will migrate the saved objects as needed.
Phase 3 - Use relationships to automatically export dependent data#27306
In this phase, we will change the export API to automatically include nested dependencies.
Phase 4 - Support import / export for any type of saved object#34862
In this phase more types of saved object will be supported for import / export and a few modifications to the saved object management UI will be made to handle UX for other types of saved object.
The text was updated successfully, but these errors were encountered: