The code checks that it's has a tty before it prompts. Automatic scripts
should work just as before using the env variable or command line
option. If they aren't present and there's no tty, then they'll error
out exactly as they did before.
Ken
On 7/16/12 2:00 PM, Adam Young wrote:
On 06/28/
On 06/28/2012 11:54 AM, Dean Troyer wrote:
On Mon, Jun 25, 2012 at 5:28 PM, Doug Hellmann
wrote:
On Mon, Jun 25, 2012 at 6:19 PM, Ken Thomas wrote:
[...]
I've already submitted the keystone changes for review
(https://review.openstack.org/#/c/8958/3/keystoneclient/shell.py) and I'd be
happy
On Mon, Jun 25, 2012 at 5:28 PM, Doug Hellmann
wrote:
> On Mon, Jun 25, 2012 at 6:19 PM, Ken Thomas wrote:
[...]
>> I've already submitted the keystone changes for review
>> (https://review.openstack.org/#/c/8958/3/keystoneclient/shell.py) and I'd be
>> happy to make the same change to UnifiedCLI
On Mon, Jun 25, 2012 at 6:19 PM, Ken Thomas wrote:
> Greetings all,
>
> Our security folks have an issue with putting passwords on the command
> line or in the environment. I wrote up a blueprint that gives the details
> on their objections as well as a proposed short-term fix for keystone (
> ht
Greetings all,
Our security folks have an issue with putting passwords on the command
line or in the environment. I wrote up a blueprint that gives the
details on their objections as well as a proposed short-term fix for
keystone
(https://blueprints.launchpad.net/keystone/+spec/prompt-for-pas
5 matches
Mail list logo