Skip to content
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

Introduce the possibility to have a log file of the migration from command line #2180

fcaponi opened this issue Oct 19, 2018 · 1 comment


Copy link

@fcaponi fcaponi commented Oct 19, 2018

Which version and edition of Flyway are you using?


If this is not the latest version, can you reproduce the issue with the latest one as well?

(Many bugs are fixed in newer releases and upgrading will often resolve the issue)

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)


Which database are you using (type & version)?

Oracle 11G Enterprise

Which operating system are you using?

Windows and Linux

What did you do?

(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)

We have config files that doesn't specify username and password, mainly for security reasons but also in order to perform migrations using different accounts.
When the migration is issued without specifying to redirect the output of the console to a file, the command line correctly ask to specify username and password to be used for the migration.
When we redirect the output to a file, the command line cannot ask for user and password anymore.
The only workaround is to specify user and password as parameters on the command line, but in such way the history of the operating system stores the password of the database.

What did you expect to see?

We would like an additional parameter on the command line in order to have the log of the migration saved for archiving purposes and the possibility to have user and password asked by the command line

What did you see instead?
@axelfontaine axelfontaine added this to the Flyway 6.0.0 milestone Oct 22, 2018
@juliahayward juliahayward removed this from the Flyway 6.0.0 milestone Jul 31, 2019
@juliahayward juliahayward added this to the Flyway 6.1.0 milestone Jul 31, 2019
Copy link

@juliahayward juliahayward commented Nov 20, 2019

Implemented in v6.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

3 participants