We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
4.0.3
Command-line
postgres, mysql
linux
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
Using a valid jdbc connection uri that includes a username and password to connect to the database, such as:
jdbc:mysql://localhost/db?user=xxx&password=xxx jdbc:postgresql://localhost/db?user=xxx&password=xxx
Results in prompt for username/password
No prompt for username/password, with the jdbc connection params used for authentication
Username/password prompts on STDIN
This worked on v3.0 and I'm trying to upgrade to v4 and ran into this issue. It looks like the following commits are relevant:
a2d1941 0e1905e
The text was updated successfully, but these errors were encountered:
40e97af
Added notes for flyway/flyway#1477
97387ab
No branches or pull requests
What version of Flyway are you using?
4.0.3
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)
Command-line
What database are you using (type & version)?
postgres, mysql
What operating system are you using?
linux
What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
Using a valid jdbc connection uri that includes a username and password to connect to the database, such as:
Results in prompt for username/password
What did you expect to see?
No prompt for username/password, with the jdbc connection params used for authentication
What did you see instead?
Username/password prompts on STDIN
This worked on v3.0 and I'm trying to upgrade to v4 and ran into this issue. It looks like the following commits are relevant:
a2d1941
0e1905e
The text was updated successfully, but these errors were encountered: