...
In order to avoid conflicts with the versioned migrations contained by default, only repeatable migrations should be used. Otherwise it may happen, that the version number of the custom script duplicates the version number of a new script provided by kgs. Leaving a larger gap, e.g. kgs scripts end at V4_0_0 and the custom script starts at V90_0_0, may block kgs scripts later added with V5 and so on. The order of the locations does not matter.
...
For example, using a custom vendor for metaservice database v2, and the scripts are located in /kgs/data/sql/vendor
| Code Block |
|---|
<repo>.metaservice.databasev2.scripts=filesystem:/kgs/data/sql/vendor |
The jar JAR files for both the driver and the flyway Flyway dependency can then be placed in a lib library folder, say /kgs/lib, and then added to the application , depending on the deployment, using the application-wide parameter loader.path, e.g. for container deployments LOADER_PATH=/kgs/lib . Read here how to apply the parameterApplication wide settings.