Disable recursive filesystem scanning down hidden directories #1807
What version of Flyway are you using?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
In my /var/flyway/data I provided only one file.
When connecting to the migraiton container and run the command manually in debug mode i have htis
$/opt/flyway/4.2.0 # ./flyway info -user=root -password=Europa01# -url=jdbc:postgresql://beosbank-posgres-db-europa/beosbank-europa -locations=filesystem:/var/
DEBUG: Java 1.8.0_131 (Oracle Corporation)
DEBUG: Loading config file: /opt/flyway/4.2.0/conf/flyway.conf
Unexpected file in the migration process
In my folder i put only one file V3.0__UpdateStreet.sql
RROR: Unexpected error
While browsing the data directory i can see only one file .
/var/flyway/data # ls
The text was updated successfully, but these errors were encountered:
I too have encountered this issue. I am trying to run flyway as an init container in my kubernetes deployment by simply using the official docker image and mounting my SQL files from a configmap onto that image.
The problem is that when kubernetes mounts the configmap containing the SQL migrations it mounts hidden files used by k8s to keep the config up to date. So if you had a directory containing only one file
with the last hidden directories being linked.
It would seem that if you specify flyway to search
I have come up with a work around of creating a custom docker image for each micro service that simply copies the SQL directory onto the image, but it would be nice to simply have the pattern of mounting the SQL files onto the official image.
Perhaps adding an option to not recurse over hidden directories would be a sufficient solution? Please let me know if this would be acceptable :D