Migrate plugin data - Githubissues

indico / indico-migrate

Utility to migrate Indico 1.2 ZODB databases to 2.0 (Postgres)

GNU General Public License v3.0

2 stars 3 forks source link

Migrate plugin data #11

Closed ThiefMaster closed 6 years ago

ThiefMaster commented 7 years ago

[ ] Chat
[ ] Invenio Importer - just settings
[ ] LiveSync - if we ignore it people need to add their agent manually and either run an initial export or set it as run via indico shell
[ ] PayPal Payment - important event settings such as the recipient of the payment
[ ] Piwik - just settings
[ ] Search Invenio - just settings
[ ] VC Vidyo

ThiefMaster commented 7 years ago

Probably best to just add it to indico-migrate and add a --plugin option (multiple=True) where we can select which plugin data should be migrated.

Vidyo and LiveSync are probably the most tricky ones since they really need the plugin to be installed for the migration as they have their own database tables.

maxfischer2781 commented 6 years ago

Not a strict requirement, but it would be nice if third party plugins could provide their own conversion plugin. For example, we use a custom ePayment plugin with its own transaction type in indico 1.2 and indico 2.0.

ThiefMaster commented 6 years ago

Since migration is a one-time thing it's better if you just clone the repo and add your own code. So far nobody needed plugin-related migrations and it'd take quite some development effort to add something nice/extensible here for little gain.

ThiefMaster commented 6 years ago

Closing this one since most people migrated by now and nobody asked for any of this plugin data to be migrated.