model-registry [feature] Add a feature to allow users to export and import model metadata

There are various use cases where users may need to be able to export and import ML model metadata:

Backup individual metadata resources
Export metadata from a registry so that it can be imported into another registry as part of a promotion of a model from a local to a shared registry.

Feb 07 '24 22:02 dhirajsb

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

May 08 '24 04:05 github-actions[bot]

I think this is a valid feature that should be available. Example, I should be able to export the model metadata from non-production environment and import into the production model registry. In cases that I heard, some will maintain a separate model registry for production so that it's completely isolated from non-production. With the export/import functionality, one can automate the process of the export and import.

May 13 '24 06:05 chengkuangan

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Aug 12 '24 04:08 github-actions[bot]

@tarilabs hi, I am interested to work on this

Aug 12 '24 04:08 antonio-pedro99

hi @antonio-pedro99 thank you for expressing your interest to work on this feature! I'm going to assign it to you, kindly keep in mind to share a proposal brief on how are you planning to design, implement this, so to ensure the work will be accepted easily :)

/assign @antonio-pedro99

Aug 12 '24 05:08 tarilabs

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Nov 11 '24 04:11 github-actions[bot]

(still needed)

Nov 11 '24 07:11 tarilabs

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Feb 10 '25 04:02 github-actions[bot]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

Mar 03 '25 04:03 github-actions[bot]

(still needed)

Mar 03 '25 07:03 tarilabs

@tarilabs is there a label to disable the stale marker?

Mar 03 '25 17:03 dhirajsb

let's see if lifecycle/frozen helps, but that so far I've seen it working only on PR

Mar 03 '25 17:03 tarilabs

i'm interested on proposing a solution in case its still a valid issue to work on. i dont see any attached pr, can i start working on it?

Mar 18 '25 14:03 mahdikhashan

thank you for your interest @mahdikhashan this is an extended feature and somehow also somehow connected to https://github.com/kubeflow/model-registry/issues/865 in the respect of the "data migration" requirement, before working on this wide topic I would coordinate with other contributors eg @Al-Pragliola

Mar 18 '25 15:03 tarilabs

thank you for your interest @mahdikhashan this is an extended feature and somehow also somehow connected to #865 in the respect of the "data migration" requirement, before working on this wide topic I would coordinate with other contributors eg @Al-Pragliola

thank you for your response, I'll reach him for further communication.

Mar 18 '25 16:03 mahdikhashan