Thanks Flowerysong...!
These answers helped me a lot..
Thanks all..!
On Tuesday, March 13, 2018 at 12:22:25 PM UTC-7, flowerysong wrote:
>
> On Tuesday, March 13, 2018 at 1:42:19 PM UTC-4, Patrick Hunt wrote:
>>
>> Good catch. You're correct, it is possible, I was mistaken. Practically
>> is i
On Tuesday, March 13, 2018 at 1:42:19 PM UTC-4, Patrick Hunt wrote:
>
> Good catch. You're correct, it is possible, I was mistaken. Practically
> is it possible to be able to provide multiple sets of credentials for your
> example? I've always done a work around, such as I listed in the other
Good catch. You're correct, it is possible, I was mistaken. Practically
is it possible to be able to provide multiple sets of credentials for your
example? I've always done a work around, such as I listed in the other
comment, since I can pass my current logon (-k) username/password, and can
On Tuesday, March 13, 2018 at 7:35:27 AM UTC-7, Patrick Hunt wrote:Hi
Patrick,
>
> I can help to address #2 at least for now.
>>
>
> Ansible does not allow you to chain "Become" statements. In other words
> you cannot log in as user1, become root, and then become user2 (or even
> user1) in th
On Tuesday, March 13, 2018 at 10:35:27 AM UTC-4, Patrick Hunt wrote:
>
> I can help to address #2 at least for now.
>>
>
> Ansible does not allow you to chain "Become" statements.
>
This is true; you cannot use two types or levels of privilege escalation at
once.
> In other words you canno
>
> I can help to address #2 at least for now.
>
Ansible does not allow you to chain "Become" statements. In other words
you cannot log in as user1, become root, and then become user2 (or even
user1) in the same play. You could address this in a few different ways
that I know of:
- split th
