Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flyway migrations of defined locations are not applied anymore #111

Closed
snowdrop-bot opened this issue Jun 18, 2020 · 0 comments
Closed

Flyway migrations of defined locations are not applied anymore #111

snowdrop-bot opened this issue Jun 18, 2020 · 0 comments
Assignees
Labels
7 - Community development upstream/closed The issue has been closed in the upstream repository

Comments

@snowdrop-bot
Copy link
Collaborator

Describe the bug
I want to use different database migrations with flyway for testing.
I defined two different locations for the flyway migrations in the application.properties:

%test.quarkus.flyway.locations=classpath:/db/migration/,classpath:/db/testing/

Expected behavior
I expect that all migrations in the folders migration and testing are applied

Actual behavior
Only the migrations in the migration folder are applied, anything in testing is ignored.

To Reproduce
Steps to reproduce the behavior:

  1. Use quarkus-flyway version newer than 1.4.2
  2. Define non-default location for flway migrations (quarkus.flyway.locations)
  3. Start application, only migrations in default path are applied

Configuration

quarkus.datasource.driver=org.postgresql.Driver
quarkus.datasource.username = ${POSTGRES_USER:postgres}
quarkus.datasource.password = ${POSTGRES_PASSWORD:postgres}
quarkus.datasource.url = ${POSTGRES_URL:jdbc:postgresql://localhost:5432/postgres}
quarkus.flyway.migrate-at-start=true
quarkus.swagger-ui.always-include=true

%test.quarkus.http.test-port=0
%test.quarkus.datasource.driver=org.testcontainers.jdbc.ContainerDatabaseDriver
%test.quarkus.hibernate-orm.dialect=org.hibernate.dialect.PostgreSQL9Dialect
%test.quarkus.datasource.url=jdbc:tc:postgresql:latest:///postgres
%test.quarkus.flyway.migrate-at-start=true
%test.quarkus.flyway.clean-at-start=true
%test.quarkus.flyway.locations=classpath:/db/migration/,classpath:/db/testing/

Environment (please complete the following information):

  • Output of uname -a or ver:
    Darwin Henriks-MBP-3.fritz.box 19.5.0 Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64 x86_64
  • Output of java -version:
    openjdk version "13.0.1" 2019-10-15
    OpenJDK Runtime Environment (build 13.0.1+9)
    OpenJDK 64-Bit Server VM (build 13.0.1+9, mixed mode, sharing)
  • GraalVM version (if different from Java): -
  • Quarkus version or git rev: 1.5.2
  • Build tool (ie. output of mvnw --version or gradlew --version):
    Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
    Java version: 13.0.2, vendor: N/A, runtime: /usr/local/Cellar/openjdk/13.0.2+8_2/libexec/openjdk.jdk/Contents/Home
    Default locale: en_DE, platform encoding: US-ASCII
    OS name: "mac os x", version: "10.15.5", arch: "x86_64", family: "mac"

Additional context
This is working in version 1.4.2.Final of quarkus-flyway but not with the newer ones.


quarkusio#10041


$upstream:10041$

@snowdrop-bot snowdrop-bot added the upstream/closed The issue has been closed in the upstream repository label Jul 16, 2020
@geoand geoand closed this as completed Sep 17, 2020
@snowdrop-bot snowdrop-bot reopened this Sep 17, 2020
@geoand geoand closed this as completed Sep 21, 2020
@snowdrop-bot snowdrop-bot reopened this Sep 21, 2020
@geoand geoand closed this as completed Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
7 - Community development upstream/closed The issue has been closed in the upstream repository
Projects
None yet
Development

No branches or pull requests

2 participants