This defeats the purpose... the reason this was suggested before was to avoid putting secrets in history files (the same can be achieved by prefixing the command with a space, of course). Doing this echo puts the password back in the history

If you want to put the password in the command line, we can use --from-literal instead of --from-file, then avoid the echo

If we're saying to use stdin in a terminal then they have to type the password and hit Ctrl+D, which we don't tell people to do right now

So really it's a balance between making the installation experience easy and risk logging password, or making the installation experience more complicated: "Oh just run this command, type your password then if you're on windows click ctrl+d or if you're on mac click cmd+d..."

I think we should use from-literal and put a warning saying it may be logged in shell history, and if they don't want that then put a space at the front

I think @sreya suggested this here: #302 (comment), you might want to check with him. I do not have strong feelings about it. It's too bad kubectl doesn't have something built-in to do this.

This way of doing it probably doesn't work on Windows, right? I also dunno about mac, presumably it's Unix-y enough that it works there? 🤷‍♂️

One other small thing: I think command lines can be seen by anyone in /proc for multi-user systems, so putting the password in the command line means that it's potentially visible to everyone logged into the system. We can just document it though, too.

I think doing it on the command line is fine. Most people aren't working on a multi-tenant box.

if it's easy or clean to show both ways so that we can avoid some rando opening a PR saying our docs leak secrets in a multi tenant system that would be ideal but either way this is pretty minor.