github (and other vcs) integration for Kibana saved objects

[LeeDr]

Describe the feature: One of the beauties of Kibana is how easy it is to create and save a new visualization (and saved searches and dashboards). But when lots of users create lots of saved objects things can get unwieldy.

• Who created these 500 visualizations?
• Who changed my favorite visualization?
• Who deleted my Saved Search
• etc.

An integration in Kibana with github (and possibly other version control systems) for saved objects could resolve a lot of these issues. I'm still thinking through some of the details but I could image a few different ways that it could work.

1. One way could be in the Saved Object page. In addition to exporting a saved object it could also show if you have uncommited objects (changes to a visualization for example). Or unstaged objects. And show the git history on the saved objects would be great.

2. Another way is right in the flow of saving an object. When you click save it would have a field for the commit comment. This might be a bit more involved to develop but I think would be better in the long run.

For either of these, you would have to use your github credentials. If you had x-pack security enabled, those credentials could possibly be stored with your password? But with 2 factor authentication it might get complicated? Otherwise each time you try to commit it would prompt for username and password?

We could also consider just saving revisions in Elasticsearch with a comment.

[elasticmachine]

Pinging @elastic/kibana-platform

[tylersmalley]

Integration with a filesystem format like Git/Github doesn't seem likely.

The functionality of versioning would need to be added to saved objects.

There is a large effort in progress around logging into a time-based indices which would allow for raising information on access to objects (visualizations/etc) into the UI.

At the very least, we should include information on who created/updated an issue which is being tracked at #51645

[pgayvallet]

If SO versioning is something that may be of interest, I think it's safe to say today that we're not planning on having any kind of VC-based versioning of any kind for it.

I'll go ahead and close this. Please feel free to reopen if anyone thinks it's worth keeping the issue.