Fix Flyway filesystem prefix location check
Co-authored-by: Andy Bell <andyrbell@gmail.com> Closes gh-13863
This commit is contained in:
@@ -2246,8 +2246,18 @@ To automatically run Flyway database migrations on startup, add the
|
||||
|
||||
The migrations are scripts in the form `V<VERSION>__<NAME>.sql` (with `<VERSION>` an
|
||||
underscore-separated version, e.g. '`1`' or '`2_1`'). By default they live in a folder
|
||||
`classpath:db/migration` but you can modify that using `flyway.locations`. You can also
|
||||
add a special `{vendor}` placeholder to use vendor-specific scripts. Assume the following:
|
||||
`classpath:db/migration` but you can modify that using `flyway.locations`. This is a
|
||||
comma-separated list of one or more `classpath:` or `filesystem:` locations. For example,
|
||||
the following configuration would search for scripts in both the default classpath
|
||||
location and the `/opt/migration` directory:
|
||||
|
||||
[source,properties,indent=0]
|
||||
----
|
||||
spring.flyway.locations=classpath:db/migration,filesystem:/opt/migration
|
||||
----
|
||||
|
||||
You can also add a special `{vendor}` placeholder to use vendor-specific scripts. Assume
|
||||
the following:
|
||||
|
||||
[source,properties,indent=0]
|
||||
----
|
||||
|
||||
Reference in New Issue
Block a user