spring-projects / spring-projects/spring-modulith
Skip nested modules when configuring flyway
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
The SpringModulithFlywayMigrationStrategy default to creating flyway tables for all modules even nested ones. Nested modules are part of a larger module and typically share the DB schema, therefore their migrations are bundled with their top level module.
It would be nice if there was a property to configure the modulith flyway strategy:
spring.modulith.runtime.flyway-strategy: all
with possible values including [all, top-level]
Also, some modules don't have any data requirement, so skipping them entirely makes sense:
spring.modulith.runtime.flyway-skip: ['email']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating SpringModulithFlywayMigrationStrategy and tracing how it creates Flyway tables for modules. Define how the strategy and skip-list properties should be bound and applied, then verify that nested modules can be excluded and configured modules can be skipped while existing behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100