On 08. aug. 2017 09:06, dogfish182 wrote:
ansible 2.3.1.0

seems to not respect the become_user in the following play.
#note that this below jams up because it expects accounts and ssh keys as
it uses rsync underwater. Figure that out then remove this comment
- name: copy dump to remote
become: false
become_user: fresh-dbs
synchronize:
mode: push
src: "{{ hostvars['192.168.56.100'].dbdump.stat.path }}"
dest: /tmp/restore.sql
delegate_to: 192.168.56.100
tags: rsync
My expectation on the above is that on the delegate host, the rsync job
should trigger as the user 'fresh-dbs' (which is created and key'd earlier
in the play
and can login to the target.

To use become_user you need to set become: true

--
Kai Stian Olstad

--
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 ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/57df7b14-5c22-d85d-c4cd-8e32b97f5e4f%40olstad.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to