Run database migrations in pre-install,pre-upgrade hook

[andydennehy]

Description

Link to issue.

This solves issue #98 by adding a pre-upgrade hook which runs pnpm -F backend migrate-production, without being constrained by startupProbe or livenessProbe.

Also, this job runs on pre-install when using an external database. To make sure all necessary environment variables are available to the migration Job, the chart creates ephemeral pre-install ConfigMap and Secret objects that are mounted into the migration container.

[almeidabbm]

Hey hey!! Thank you for you contribution 🚀
This looks mostly good although I do have a couple suggestions

Also, in the PR description you mention changing the entrypoint to node dist/index.js, this change isn't here but I do think it should be kept out so that pods still run migrations if they just get their new version via a kubectl command (not upgraded via helm)

[almeidabbm]

Can this also include initContainers?
Some infra's might be using them as side car containers serving as proxy for the db which would be necessary to run migrations 😄

[andydennehy]

Done!

[andydennehy]

Hey hey!! Thank you for you contribution 🚀 This looks mostly good although I do have a couple suggestions

Also, in the PR description you mention changing the entrypoint to node dist/index.js, this change isn't here but I do think it should be kept out so that pods still run migrations if they just get their new version via a kubectl command (not upgraded via helm)

Yes, that was my initial idea but we can leave it like this. It shouldn't matter as long as the migration runs before the backend pods starts...