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

New objects API export without dependencies from the UI #22550

Closed
AlonaNadler opened this issue Aug 30, 2018 · 6 comments · Fixed by #33513
Closed

New objects API export without dependencies from the UI #22550

AlonaNadler opened this issue Aug 30, 2018 · 6 comments · Fixed by #33513
Labels
Feature:Kibana Management Feature label for Data Views, Advanced Setting, Saved Object management pages Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@AlonaNadler
Copy link

AlonaNadler commented Aug 30, 2018

The new object API was planned to allow users to export the object with the dependencies from the UI, for example when exporting a dashboard it will export the dashboard with the visualizations, that is a popular request when trying to move dashboards between different Kibana instances. Currently, the saved object API supports it but the request is to be able to do it from the UI. In early PR of this feature, before it was merged it did work, and I was able to export the dashboard and have all the visualizations included, I'm not sure whether it's a regression or decision that was made.

@chrisronline do you remember this issue?
cc: @elastic/kibana-management @yaronp68

@chrisronline
Copy link
Contributor

I can't recall if we intentionally didn't want this behavior. Correct me if I'm wrong, but I think the current export feature does not support exporting dependencies and I'm not sure if it did before. You can just export everything to ensure all dependencies are contained, but I don't think we have a working solution for exporting a single dashboard and ensuring all the dependent visualizations/saved searches/index patterns are auto exported as well

@bmcconaghy
Copy link
Contributor

Pretty sure this did work at some point. I know we intended for it to work in that fashion anyway.

@AlonaNadler
Copy link
Author

@chrisronline you are the current export doesn't include the dependencies, exporting everything doesn't really solve common customer problem where they want to export specific dashboard and tracking all the dependencies is difficult especially if they have a large number of dependencies.
@bmcconaghy yes I also recall it worked at some point and both @alexfrancoeur and I were under the impression the new object API will allow us to solve this need

@AlonaNadler
Copy link
Author

With Spaces this is even more important to have the dependencies since users will want to manage objects and move objects between the different Spaces using the UI, if it won't have the dependencies it will be much more difficult to manage spaces and the objects

@epixa
Copy link
Contributor

epixa commented Sep 11, 2018

A UI for this would depend on #16831

@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Kibana Management Feature label for Data Views, Advanced Setting, Saved Object management pages Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed :Management DO NOT USE labels Nov 27, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Kibana Management Feature label for Data Views, Advanced Setting, Saved Object management pages Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants