-
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
Expose object import/export as an API #4759
Comments
+1 |
2 similar comments
+1 |
+1 |
Related to #5480 |
+1 |
+1 |
+1 |
2 similar comments
+1 |
+1 |
+1, we'd like to promote saved searches alongside logging code releases in our release pipeline. |
༼ᕗຈل͜ຈ༽ᕗ +1 |
+1 |
1 similar comment
+1 |
+1! |
+1 |
1 similar comment
+1 |
+1 |
+1. It would be great to build these visualization objects on a dev machine, commit to git and as part of deploy process update then on test/prod environments. |
@dmitrypol This issue is specifically for REST APIs for export/import. Follow #2310 for loading objects from the file system. |
could I just +1 👍 |
Hey there Mike, |
Hi @JoaoFranciscoCarvalhoNeto, a pull request is on its way to resolve this. I have to finish the relationships aspect first #27210. |
Thanks @mikecote! Keep up the wonderful work |
Fixed by #33513. |
In order to satisfy automatically exporting dependent saved objects #27203, having the export and import logic on the server side will facilitate object manipulation.
Proposed would be three new rest API endpoints:
/api/management/saved_objects/_export
/api/management/saved_objects/_import
/api/management/saved_objects/_resolve_import_conflicts
Notes:
Original description
It would be great to move saved object import/export as a rest API. This requires that savedObjects can be used on the server, but seems like a worthwhile goal so that savedObject manipulation can be a bit more automated.
The text was updated successfully, but these errors were encountered: