Migrations for App-Schema combinations

[connoratrug]

Issue

Currently the molgenis-emx2 codebase contains en number of (frontend)apps that expect a certain (backend)model. Examples are the 'catalogue app', the 'directory app' , ... . This means that for the service to function, the app en model need to be kept in sync. Currently we do not have a automated solution to support the synchronisation.

Solution

Add changes to models associated app to be updated via a migration system

• Add data to the molgenis system tabel to store the link between a 'schema' and a 'app'
• Update the admin interface to manage these links
• Create a per app directory structure that contains java/sql file for each migration step.
• Add some code that ( onstartup , on trigger ) check if migrations need to run en them.

Alternatives

• do nothing, keep doing migration by hand
• do the migration via the outside ( combination if python and tasks )

Additional context

See emx2 migration as an example for the general idea