New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flyway initSql support #16226
Labels
Milestone
Comments
/cc @cristhiank, @gastaldi, @geoand, @gsmet |
Is the issue was assigned or can I work on this Sir? |
You can work on it if you like |
Sure Sir |
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Apr 9, 2021
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Apr 9, 2021
@srisatya1197 hey, I just saw the conversation now. I needed this feature so I provided a PR, hope you don´t mind? 😃 |
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Apr 9, 2021
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Apr 9, 2021
@gastaldi No worries Sir. |
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Apr 10, 2021
Fixes quarkusio#16226 (cherry picked from commit 5c36168)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
Flyway has an initSql property to specify sql to run. This is useful e.g. for selecting a role in PostgreSQL to use for the migration. This is beneficial if you use vault generated users who also need to update schemas. Currently it cannot be specified in the extension configuration. I think it would be a good addition.
The text was updated successfully, but these errors were encountered: