Re: [ansible-project] Re: Playbook that uses become only if root user not specified?

2017-07-05 Thread ajay jiwanand
I thought become: True and become: yes are "the same"?! > > Am Dienstag, 4. Juli 2017 20:06:29 UTC+2 schrieb ajay jiwanand: >> >> A very simple fix was to just change become:true to become:yes and root >> authentication works as long as you dont specify sudo passwor

[ansible-project] Re: Playbook that uses become only if root user not specified?

2017-07-04 Thread ajay jiwanand
A very simple fix was to just change become:true to become:yes and root authentication works as long as you dont specify sudo password in command line (-K) and specify root account with -u On Tuesday, July 4, 2017 at 1:46:05 PM UTC-4, ajay jiwanand wrote: > > Hey Daniel, > > Tha

[ansible-project] Re: Playbook that uses become only if root user not specified?

2017-07-04 Thread ajay jiwanand
' no luck On Tuesday, July 4, 2017 at 2:05:37 AM UTC-4, Daniel JD wrote: > > You could use something like the following: > > - name: Set sudo Passwort > set_fact: > ansible_become_pass: "{{ my_encrypted_password }}" > when: ansible_user == 'non-root-u

[ansible-project] Playbook that uses become only if root user not specified?

2017-07-03 Thread ajay jiwanand
I am writing a playbook that will cover a wide ranged of hosts some that is integrated into AD with sudo privileges and others with just a local "root" account. I currently have the playbook written with the become module and it works fine for AD integrated hosts but when i specify a root user i

[ansible-project] Re: Multiple and/or conditions in when wont work

2017-06-30 Thread ajay jiwanand
use the intersect filter from jinja2. > > I am thinking about sth. like the following: > > when: ansible_os_family == "RedHat" and not vars.keys() | > intersect([security,kernel,specified_packages]) > > Am Donnerstag, 29. Juni 2017 23:34:16 UTC+2 schrieb ajay jiwanand

Re: [ansible-project] Re: Multiple and/or conditions in when wont work

2017-06-30 Thread ajay jiwanand
ed or specified_packages is defined) and ansible_os_family == "RedHat" Thanks! On Friday, June 30, 2017 at 2:48:02 PM UTC-4, Kai Stian Olstad wrote: > > On 30. juni 2017 19:10, ajay jiwanand wrote: > > Im posting my stack overflow question as it is much more clear: > &

[ansible-project] Re: Multiple and/or conditions in when wont work

2017-06-30 Thread ajay jiwanand
writes the playbook in a more efficient way as I am sort of a noob. On Thursday, June 29, 2017 at 5:34:16 PM UTC-4, ajay jiwanand wrote: > > I am having issues with using multiple conditions in when to validate > whether or not to run a task. > > Basically I am using extrended varia

Re: [ansible-project] Multiple and/or conditions in when wont work

2017-06-30 Thread ajay jiwanand
i want to run the task when ansible_os_family == "RedHat" (this works) AND if none of the following variables are set (security,kernel,specified_packages) through extended variables (-e) On Friday, June 30, 2017 at 2:17:29 AM UTC-4, Kai Stian Olstad wrote: > > On 29. juni

Re: [ansible-project] Multiple and/or conditions in when wont work

2017-06-30 Thread ajay jiwanand
I want the task to run if the os if redhat (this conditional works fine) and when either of the following extended vars are set security/specified_packages/kernel. On Friday, June 30, 2017 at 2:17:29 AM UTC-4, Kai Stian Olstad wrote: > > On 29. juni 2017 23:00, ajay jiwanand wrote: &g

[ansible-project] Multiple and/or conditions in when wont work

2017-06-29 Thread ajay jiwanand
I am having issues with using multiple conditions in when to validate whether or not to run a task. Basically I am using extrended variables within the ansible command to state what sort of updates I want to run like this: ansible-playbook site.yml -i inventory --ask-vault -u (username)-e "secu