Update keyvalue.py to be able to add new values without leaking them in the shell history.

[wingiti]

Add possibility to add a value by using a prompt instead of a parameter. This prevents secrets from being documented/leaked in the shell history.

[CLAassistant]

All committers have signed the CLA.

[Kami]

There is also getpass.getpass() which displays entered value masked on the screen.

But if we go with that approach, we will likely need to ask for confirmation (aka input the secret value twice).

[wingiti]

Is there anything you want to change here or will it be implemented in version 3.5? Nevertheless it is possible to check the value after it was inserted in the key value store.

[cognifloyd]

In a future PR, I think we could add getpass.getpass() support, but only turn it on if encrypt is True. I think this PR is good enough to merge as is.

[cognifloyd]

We just reformatted the code with black. (Hooray!) And this PR got caught in the cross fire too. (Arrgh!)
Please merge master into your branch, resolve the conflicts (Ouch! Sorry!), and reformat with black (I recommend running pre-commit install after you've merged master so that black reformatting happens automatically on commit).

[arm4b]

The tests look 💚 again.

I expect @Kami to review it again, but @wingiti can you please also add the Changelog.rst record for this PR? We'll need it anyways.

Thanks!

[cognifloyd]

In a future PR, I think we could add getpass.getpass() support, but only turn it on if encrypt is True. I think this PR is good enough to merge as is.

[wingiti]

@Kami do you want to approve this? Would be nice, otherwise I have to overwrite this all the time after a Stackstorm upgrade in my local installations.

[amanda11]

@wingiti The lint checks are failing as there is trailing space on the CHANGELOG.rst.

Could you amend, and check if you have signed the CLA (there was a new version issued, so you may have to re-sign).

Many thanks.