-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add password getter system for customize getting password. (#298) #299
Conversation
1. Add AskPasswordGetter (ask password before connecting) 2. Add CallabackPasswordGetter (gets password with call callbacks, Closures)
Cool! 👍 |
Ok. I not see "symfony/console": "~2.6" And i checks the |
Test coverage decreaseв a little bit. If you can keep them on same level, it will be 100% awesome 👍 But if not, nothing terrible, leave it as it is. PS Where are a lot issue to implement too, if you want take a look at #297. |
I think PhpSecLib used to ask for password if it was empty, is that correct? |
@Max-Might Yes, because password prompt before connection (in configuraiton Example for ask password: server('production', 'domain.com')
->user('user')
->password() // <-- Default null (If null, the AskPasswordGetter will be created automatically)
->stage('production')
->env('deploy_path', '/var/www/domain.com'); |
Cool feature. |
Will this work for passphrase in identityFile function? |
@DirtyB, no, but this easy add. |
Can you implement this too?
|
ok. |
Adds. Attention: by default, passphrase - '' (empty string). For use password getter automatically, you must set ->identityFile(null, null, null) P.S. Can set the null value for |
Thats ok, pass must be ‘’ as default. |
Nice work. Need same one else too look at the PR before i'll merge it. |
ping |
I tested this feature, look good. Guys, please, test this feature too! |
Add password getter system for customize getting password. (#298)
@ZhukV i'm going to implement event dispatcher in Deployer. Can you rewrite your feature by using dispatcher later? |
👍 No problem! |
For more information, please see #298