On 29 March 2015 at 04:29, Vince Skahan <[email protected]> wrote:
The new syntax is unclear to me, and I'm not understanding why you > deprecated the old clear/concise syntax. > Actually, I think the new -b option makes sense in general. It avoids the need to add new command-line parameters for additional privilege escalation methods. However, I was just concerned that I needed to type --ask-become-pass each time, instead of a short option. So either allowing -K to keep working, or introducing a new short option for password prompting would be good. I notice that lowercase 'p' is still unused. How about making '-p' short for --ask-become-password? Then, ansible would figure out the become method, and prompt accordingly. So I could type: ansible -bp and ansible would prompt: sudo password: If I also add --become-method=su (or set it in ansible.cfg), then ansible would prompt for the "su" password. Anand -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CANbPJF%3D3v5BK9DzeYZF%2B7AvNAyXOZ-GFN0TMkciSuLEc%3D4-oCQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
