Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Generate "src/main/resources/db/migration" structure for Flyway projects

See original GitHub issue

Out-of-the-box, the ApplicationTests.contextLoads() test will fail with a generated project that uses Flyway because there’s no default migration file.

Adding an empty V1__init.sql file into the resources/db/migration directory would make that test pass and be a nicer experience.

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:6 (4 by maintainers)

Top GitHub Comments

2reactions

wilkinsonacommented, Jan 10, 2019

That sounds reasonable to me. On the Boot side, perhaps we should consider some failure analysis for the exception that Flyway throws as well?

0reactions

tedyoungcommented, Jan 10, 2019

So it looks like Boot is the one complaining as part of autoconfigure (see https://github.com/spring-projects/spring-boot/blob/2.1.x/spring-boot-project/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration.java#L191)

For adding Flyway to an existing Boot project that already has database schemas, etc., that check makes sense, but for a newly generated project, it’s confusing (“how can I write a migration when I don’t have any code yet?”). I feel like there needs to be better guidance, though I agree that generating an empty migration, which then has to be modified or thrown away, might not be best.