Open fgimian opened 6 years ago
I think this would be a good opportunity to clarify the use cases for which --skip-prompt
is intended.
One scenario where the current behaviour has been desirable is with automation scripts that need to run without human intervention: often in these cases, it's useful to have the command fail rather than hang on a prompt.
The other factor that may need consideration is the (admittedly, not all that well documented) ability to use a SAML2AWS_PASSWORD
environment variable to supply the password instead of the command line flag, making it possible to avoid prompting while also not having to use the --password
option on the command line.
I would also like to have an option to skip the username prompt. Sometimes I accidentally start typing my password when the username is prompted which is then visible in cleartext. This might happen while sharing my screen which would be really bad. Having an option to skip the username prompt would prevent this. This could even be the default behavior. Why are you prompted to enter a username if it is already given in the command line?
It is undesirable to use the
--password
option due to safety. but-skip-prompt
is at least useful to skip the Username prompt. However, this is what happens:This works as expected for the MFA token input with the
--skip-prompt
option:Cheers Fotis