spring:
  application:
    name: db-migrations-flyway-liquibase
  datasource:
    url: jdbc:h2:file:./data/quickstart;AUTO_SERVER=TRUE
    username: sa
    password: ""
  flyway:
    enabled: true
  liquibase:
    enabled: false
    change-log: classpath:db/changelog/db.changelog-master.yaml

management:
  endpoints:
    web:
      exposure:
        include: flyway,liquibase,health

---
# ./scripts/run.sh both-naive — both tools enabled against the same fresh database, no other
# configuration. Fails to start: Liquibase's SpringLiquibase bean runs before Flyway's, so by the
# time Flyway checks the schema it finds tables it doesn't recognize. See docs/14-running-both-at-once.md.
spring:
  config:
    activate:
      on-profile: both-naive
  datasource:
    url: jdbc:h2:file:./data/both-naive;AUTO_SERVER=TRUE
  liquibase:
    enabled: true

---
# ./scripts/run.sh both-fixed — the fix from docs/14-running-both-at-once.md applied: Flyway is
# told to baseline the schema Liquibase already built, starting from "nothing has run yet"
# (baseline-version: 0) rather than the default "version 1 already ran" baseline.
spring:
  config:
    activate:
      on-profile: both-fixed
  datasource:
    url: jdbc:h2:file:./data/both-fixed;AUTO_SERVER=TRUE
  liquibase:
    enabled: true
  flyway:
    baseline-on-migrate: true
    baseline-version: 0