Improve database migrations process
Issue
Running DB migrations on our Kubernetes cluster currently requires logging into the running container and manually entering the migration commands there. Also, the normal DB user does not have enough rights to create tables, for example. Therefore, currently the CV container has to be started first with the admin DB user to then run the migration scripts. Then start the container again with the normal user. All very complex and you always need someone with cluster access.
Possible solutions
- I would therefore like there to be a button in the CV admin area where these migrations can be triggered. In addition, the DB-Admin-User would have to be passed as an extra variable and used for this.
- Another possibility would also be to automatically execute the migrations whenever the container is redeployed (the app is booted).