Fixes #209 - Impossible to run platform services on a shared database

[andrea-gioia]

Fix Impossible to run platform services on a shared database (#209)

What does this PR do?

This pull request adds the flyway. schemas property to the docker application profile of each platform service to save the flyway_schema_history table in the same schema used by the service and not in the public schema. This prevents conflict and fixes the issue of running multiple platform services on a shared database.

Changes made:

• Added property fltway.schemas: to docker profile of blueprint service
• Removed flyway.schemas property from all modules' testmysql and localmysql application profiles beacause this property have no sense on MySLQ
• Removed all occurrences of double semicolons improperly used to end lines in the code

How to test:

Build code...

git clone git@github.com:opendatamesh-initiative/odm-platform.git
cd ./odm-platform
mvn clean install -DskipTests

Run Postgres container...

docker network create odmp-network
docker run --name odmp-postgres -d --network odmp-network -p 5432:5432 \
  -e POSTGRES_DB=odmpdb \
  -e POSTGRES_USER=postgres \
  -e POSTGRES_PASSWORD=postgres \
  postgres:11-alpine

Run registry container...

docker build -t odmp-postgres-registry . -f product-plane-services/registry-server/Dockerfile \
   --build-arg DATABASE_URL=jdbc:postgresql://odmp-postgres:5432/odmpdb \
   --build-arg DATABASE_USERNAME=postgres \
   --build-arg DATABASE_PASSWORD=postgres \
   --build-arg FLYWAY_SCRIPTS_DIR=postgresql


docker run --name odmp-postgres-registry  -d --network odmp-network -p 8001:8001 odmp-postgres-registry

Run notification container...

  docker build -t odmp-postgres-notification . -f product-plane-services/notification-server/Dockerfile\
   --build-arg DATABASE_URL=jdbc:postgresql://odmp-postgres:5432/odmpdb \
   --build-arg DATABASE_USERNAME=postgres \
   --build-arg DATABASE_PASSWORD=postgres \
   --build-arg FLYWAY_SCRIPTS_DIR=postgresql


docker run --name odmp-postgres-notification  -d --network odmp-network -p 8006:8006 odmp-postgres-notification

Restart containers...

docker stop odmp-postgres-registry
docker stop odmp-postgres-notification
docker start odmp-postgres-registry
docker start odmp-postgres-notification

The restart of services MUST be completed successfully.

🔴 WARNING 🔴 Before running the new version of a service during an upgrade, the existing flyway_schema_history table must be copied from the previous schema (typically public) to the specific schema used by the service. For example, for the registry service, the following instruction should be executed in PostgreSQL to replicate the flyway_schema_history table within the ODMREGISTRY schema

create table "ODMREGISTRY"."flyway_schema_history" as select * from "public"."flyway_schema_history"