anchor.diff:  ==== Execute Liquibase Database Migrations on Startup
   To automatically run Liquibase database migrations on startup, add the `org.liquibase:liquibase-core` to your classpath.
   
  +[NOTE]
  +====
  +When you add the `org.liquibase:liquibase-core` to your classpath, by default database migrations will run for both during application startup and before your tests run.
  +This behavior can be customized by using the configprop:spring.liquibase.enabled[] property, setting different values in the `main` and `test` folders.
  +It is not possible to use two different ways to initialize the database (e.g. Liquibase for application startup, JPA for test runs).
  +====
  +
   By default, the master change log is read from `db/changelog/db.changelog-master.yaml`, but you can change the location by setting `spring.liquibase.change-log`.
   In addition to YAML, Liquibase also supports JSON, XML, and SQL change log formats.
   
  
positive.code: If you do so and you want two data sources, remember to create another one and mark it as `@Primary`.
  Alternatively, you can use Liquibase's native `DataSource` by setting `spring.liquibase.[url,user,password]` in external properties.
  Setting either `spring.liquibase.url` or `spring.liquibase.user` is sufficient to cause Liquibase to use its own `DataSource`.
  If any of the three properties has not be set, the value of its equivalent `spring.datasource` property will be used.
  
  See {spring-boot-autoconfigure-module-code}/liquibase/LiquibaseProperties.java[`LiquibaseProperties`] for details about available settings such as contexts, the default schema, and others.
  
  
negative.code: 
  [NOTE]
  ====
  When only basic SQL scripts are used, Spring Boot automatically creates the schema of an embedded `DataSource`.
  This behavior can be customized by using the configprop:spring.datasource.initialization-mode[] property.
  For instance, if you want to always initialize the `DataSource` regardless of its type:
  
  