#262: Full Flyway integration

[benedeki]

• numbered the SQL scripts for Flyway
• changed PartitioningForDB class to contain keysToValuesMap instead of keysToValues according to validation
• added sbt alias testAll for running all tests
• database test for validation function moved to proper folder
• set flywayBaselineVersion for upgrade purposes

While it's almost 70 files, changes are minimal. In majority of cases it's just a rename.

---

For the actual upgrade deployment these steps are necessary:

Manual:

sbt -Dflyway.url=<target db url> -Dflyway.password=<postgres user password> flywayBaseline

Add to deployment automation

sbt -Dflyway.url=<target db url> -Dflyway.password=<postgres user password> flywayMigrate

where

• <target db url> is the database towards which the deployment is running, e.g. "jdbc:postgresql://localhost:5432/atum_db"
• <postgres user password> is the password for the postgres super user at the above database

---

Depends on #265
Depends on #267
Depends on #272
Depends on #275

Closes #262

Release notes:

• Reordered and fixed database structure scripts to allow Flyway usage for incremental migration of existing database (version 0.1.x). Known issues: there might be needed some manual steps if upgrading from database of version 0.2.0.

[github-actions]

JaCoCo model module code coverage report - scala 2.13.11

Overall Project	63.64%	🍏

There is no coverage information present for the Files changed

[github-actions]

JaCoCo agent module code coverage report - scala 2.13.11

Overall Project	84.63%	🍏

There is no coverage information present for the Files changed

[github-actions]

JaCoCo reader module code coverage report - scala 2.13.11

Overall Project	100%	🍏

There is no coverage information present for the Files changed

[github-actions]

JaCoCo server module code coverage report - scala 2.13.11

Overall Project	72.57% -0.08%	🍏
Files changed	76%	❌

File	Coverage
PartitioningRepositoryImpl.scala	100%	🍏
PartitioningForDB.scala	100% -13.64%	❌
GetFlowPartitionings.scala	70.96%	🍏

[benedeki]

Release notes:
Reordered and fixed database structure scripts to allow Flyway usage for incremental migration of existing database (version 0.1.x). Known issues: there might be needed some manual steps if upgrading from database of version 0.2.0.

[benedeki]

This item depends on:

• Feature/230 get partitioning checkpoints #265
• Feature/235 get flow partitionings #267
• Feature/234: GET main flow of a partitioning #272
• get partitioning #275
  By Dependent Issues.

[lsulak]

LGTM, found a few minor things. But I want to ask: why the numbering like this? For example there is no V0.1.0.3.{sql|ddl} file, so there are gaps. There is V0.1.0.30.ddl instead. So we don't want increments?

[benedeki]

LGTM, found a few minor things. But I want to ask: why the numbering like this? For example there is no V0.1.0.3.{sql|ddl} file, so there are gaps. There is V0.1.0.30.ddl instead. So we don't want increments?

It is incremental, but with gaps.
I put the gaps there between folders/schemas number ranges, so in case of testing, if something has to change, I won't be forced to renumber everything. And it actually happened 😉