Open Stack

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/2012 11:54 AM, Dean Troyer wrote:
>> On Mon, Jun 25, 2012 at 5:28 PM, Doug Hellmann
>> <doug.hellmann at dreamhost.com> wrote:
>>> On Mon, Jun 25, 2012 at 6:19 PM, Ken Thomas <krt at yahoo-inc.com> 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 as well.
>>> Thanks, Ken! That sounds like a good change to make. If you add me as a
>>> reviewer on the patch, I'll make sure to look at the changes.
>> I created a blueprint for this:
>> https://blueprints.launchpad.net/python-openstackclient/+spec/password-prompt
>> linking back to the keystone blueprint.  That looks like a good
>> solution.
>>
>> Thanks Ken
>> dt
>>
> Probably would be better to have a deliberate command line flag for it,
> so automated scripts don't hang.
>
> Something like --prompt
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp