You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I'm using sqlx-cli inside container to run postgres migrations for my app (I like applying migrations separately, not with my main app). It worked great when I was using docker containers with volume binds. Lately I started migrating my app to kubernetes where volume binds are not the way to inject config into app. Instead You use ConfigMaps which are then injected into container as directory consisting of symlinks to content of ConfigMap. I think this caused my migrations container to 'break'. Is it something that could be supported by sqlx-cli or is there good reason to avoid it?
This is the code that I think is responsible for ignoring symlinks:
Hello, I'm using sqlx-cli inside container to run postgres migrations for my app (I like applying migrations separately, not with my main app). It worked great when I was using docker containers with volume binds. Lately I started migrating my app to kubernetes where volume binds are not the way to inject config into app. Instead You use ConfigMaps which are then injected into container as directory consisting of symlinks to content of ConfigMap. I think this caused my migrations container to 'break'. Is it something that could be supported by sqlx-cli or is there good reason to avoid it?
This is the code that I think is responsible for ignoring symlinks:
sqlx/sqlx-core/src/migrate/source.rs
Lines 27 to 30 in 1227d5d
The text was updated successfully, but these errors were encountered: