Create sample second flyway process for core data model work #287
+16
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minimal amount of work to get a second flyway container running locally that only looks at core data model migrations
Does not address running a second flyway process in AWS or update the flyway container to pack in core data model migrations.
Note: This puts the flyway schema history table for the core data model under a "cdm" schema for convenience (it wasn't immediately obvious how to put two different flyway schema history tables on public and this works)
Usage:
docker compose upfrom npd root directory will run a new cmd-migrations service, which creates a cdm schema, a flyway schema history table, and an address table. The contents ofcdm/migrations/V1__create_initial_schema.sqlare throwaway, do whatever you want with that.