[MD]Handle data source export

[seraphjiang]

OSD allow users to export saved objects as JSON, need to handle the credential properly (as plain text or hash)

[kristenTian]

Dropping the hashed credentials instead.

[vvvprabhakar]

Any update on this ? I am looking out for this feature, where in i get a export button in my saved objects listing page (Vizs or Dashboards) where user can get saved object json of it and where ever he want he can import and create a same saved object ?

If you need any specific help i am ready for it

[zhongnansu]

adding a github issue related to this topic. cc: @seraphjiang @zengyan-amazon
#4529

[zhongnansu]

It's valid use case as @vvvprabhakar mentioned, that we should support export/import data source.
A few things in my mind, if we

• export password as explicit text: this approach is not secure enough. The user has permission to export may not always be the user that has the permission to the credentials
• export password as encrypted text (same as how password is saved in index): we need to make code changes, so when import triggers creating data source with encrypted credentials, it won't treat it as a "new" password that needs to be encrypted.

[kgcreative]

Should data source connections be exportable? It makes me think that endpoint and other information could be, but the credential details should definitely not be