Move migrations out of core

[mgdenno]

We should consider moving the migrations of core and into the individual deployments since the best partition scheme may not be the same across deployments. Each deployment should start with the migration ins teehr as a starting point.

@samlamont @jbkolze Thoughts?

[jbkolze]

I don't have my head completely into the full suite of migrations, but my assumption is that there are at least some migrations that will need to be included in all deployments -- things that the core teehr workflows will expect to be completed. Would it make sense to keep that sort of thing in the core and migrate any custom migrations into the deployment, then update migration scripts to run once for the core and once for the deployment? Would likely require a little thought into making sure things run "in order".

I just worry about a situation in which a "required" migration gets dropped in one of the deployment repos and breaks the core teehr functionality. This might add some complication assuming that the "core" tables are the ones being repartitioned, though, since they'd have to be altered with partitions rather than partitioning on creation.

That being said, I don't have any real qualms with completely separating the migrations if that looks like the cleanest route. Will just be a little more manual work to make sure all deployments are "in sync".

[mgdenno]

For reference the minimum table requirements for TEEHR to work are in the teehr repo here: https://github.com/RTIInternational/teehr/tree/main/src/teehr/migrations. I think those are the "core" tables needed. Currently when a change is made in teehr it has to be manually propagated to all deployments...not ideal, but it works.

[samlamont]

I think separated the migrations by deployment makes sense. I'm wondering if we should create a method in teehr to run the teehr migrations like ev.apply_migrations() then when updating a deployment it could first run the teehr migrations using this method then apply any deployment-specific migrations like we currently do (ref: https://github.com/RTIInternational/teehr-hub/blob/main/warehouse/04_maintenance/00_apply_migrations.ipynb)

That way we wouldn't have duplicates between teehr and the deployments?