anchor.diff:  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.
  +If any of the three properties has not been 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.
   
  
positive.code: ----
  	spring.datasource.initialization-mode=always
  ----
  ====
  
  By default, Spring Boot enables the fail-fast feature of the Spring JDBC initializer.
  This means that, if the scripts cause exceptions, the application fails to start.
  You can tune that behavior by setting `spring.datasource.continue-on-error`.
  
  NOTE: In a JPA-based app, you can choose to let Hibernate create the schema or use `schema.sql`, but you cannot do both.
  Make sure to disable `spring.jpa.hibernate.ddl-auto` if you use `schema.sql`.
  
  
  
  
negative.code: ==== 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.
  
  