Authentication Failure -> should interrupt deployment

[Former user]

An authentication failure is not stopping the deploy -> every host will return a failure. Depending on your pw-policy a host list > x will lock your account.

A deployment should query for a new common pw or the user should be able to ignore that specific host.

[Travis Bear]

Good catch. I've encountered this as well.

[Travis Bear]

Each deployment happens more or less simultaneously in a separate thread. By default, ssh-deploy-key creates 100 threads to process the list of remote hosts. 100 login failures may be enough to trigger the lockout, so this is not a straightforward fix.

[Travis Bear]

Fixed in PR#1