Skip to content

Conversation

@wbprice
Copy link
Contributor

@wbprice wbprice commented Dec 19, 2025

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.

Screenshot 2025-12-19 at 4 25 55 PM

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 up from 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 of cdm/migrations/V1__create_initial_schema.sql are throwaway, do whatever you want with that.

@rmillergv
Copy link
Contributor

great starting point, thanks!

@wbprice wbprice marked this pull request as draft December 19, 2025 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants