Indicating username with delegate_to

[Joshua Swink]

Is there a way to indicate the remote username when using delegate_to? I'm trying to use the Nagios plugin, but it tries to log in to the Nagios server as the name of the user on the service host. Here's my example recipe for shutting down a service:

---
- hosts: abc_hosts
  serial: 1
  tasks:
  - name: Disable Nagios alerts
    nagios: host={{ ansible_ssh_host }} action=silence
    delegate_to: nagios.myplace.xyz
  - name: Disable ABC service
    shell: service ABC stop

If the username on abc_hosts is "abc" and the username on the Nagios server is "nagios", the plugin will try to log in to nagios.myplace.xyz as "abc". I need it to use user "nagios" here.

[Michael DeHaan]

Delegate_to will use the same credentials.

I think this would warrant something like "delegate_user:" as a new keyword.   If anyone wants to have at it, it would likely be accepted.

--
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-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Michael DeHaan <mic...@ansibleworks.com>
CTO, AnsibleWorks, Inc.
http://www.ansibleworks.com/

[Brian Coca]

remote_user: on the same task should do just that.

[Michael DeHaan]

Yeah, this is true.  Point!

Just start a new play for that task and start a new play immediately after if need be.

We should prefer this to a new keyword.

- hosts: webservers

  remote_user: foo

  tasks:

     - ...

- hosts: webservers

  remote_user: nagios

  tasks: 

     - ...

- hosts: webservers

  remote_user: foo

  tasks:

     - ...

On Mon, Nov 25, 2013 at 9:00 PM, Brian Coca <bria...@gmail.com> wrote:

remote_user: on the same task should do just that.

--

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-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Brian Coca]

since 1.4 you should not need to do it at play level, you should be able to specify remote_user: at task level too.

[Michael DeHaan]

Indeed, this is why I keep you around, sir :)

On Mon, Nov 25, 2013 at 9:15 PM, Brian Coca <bria...@gmail.com> wrote:

since 1.4 you should not need to do it at play level, you should be able to specify remote_user: at task level too.

--

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-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Ken Lemoine]

I'd be interested.  Cannot seem to find a way to use delegate_to with a different username.  Has anyone figured out a  workaround?

[Michael DeHaan]

See what Brian said in this very thread about setting "remote_user" on the task.

--

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-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Ken Lemoine]

Yes I saw that as soon as I sent that post. LOL. Thx!

Sent from my mobile.  Please excuse the brevity, spelling & punctuation.

You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/-gr3k70JNlw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.