-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Saved objects export - unable to export when references are missing #43876
Copy link
Copy link
Closed
Labels
Feature:Kibana ManagementFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature:Saved ObjectsTeam:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience
Metadata
Metadata
Assignees
Labels
Feature:Kibana ManagementFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature:Saved ObjectsTeam:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience
Type
Fields
Give feedbackNo fields configured for issues without a type.
The Saved Objects Export API (and corresponding UI feature) can optionally retrieve all references when exporting saved objects.
If the requested object references a non-existent object, the export operation will fail altogether.
I think it would be better if the export succeeded, or at least allowed for partial success.
curl 'http://localhost:5601/api/saved_objects/_export' -H 'kbn-version: 8.0.0' -H 'Content-Type: application/json' --data-binary '{"objects":[{"id":"722b74f0-b882-11e8-a6d9-e546fe2bba5f","type":"dashboard"}],"includeReferencesDeep":true}'