Right now, if a user has account test with username test@test.com attached to it with a generated password and enters rypass a -a test -u test@test.com the program will automatically (and without mercy) overwrite the password for that username. This should NOT happen.
A warning message should be raised saying 'You are about to overwrite the password for USERNAME attached to ACCOUNT. Do you want to continue (y/n)?'
If they answer yes or y, then the program should overwrite the password and display a success message printing out the old password and the new password.
If they answer no or n, then the program should stop executing and leave the account and username data alone.
Right now, if a user has account
test
with usernametest@test.com
attached to it with a generated password and entersrypass a -a test -u test@test.com
the program will automatically (and without mercy) overwrite the password for that username. This should NOT happen.A warning message should be raised saying 'You are about to overwrite the password for
USERNAME
attached toACCOUNT
. Do you want to continue (y/n)?'If they answer
yes
ory
, then the program should overwrite the password and display a success message printing out the old password and the new password.If they answer
no
orn
, then the program should stop executing and leave the account and username data alone.