you can still override it at run/play level, it is just not with
remote_user, you need to set/unset ansible_ssh_user
--
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 em
It's a "can't win em all" thing.
In one case, you want a way to override all behavior, in another, you want
a way to set a default.
In most cases, if you make a host with a given username/pass coupled to it,
it means "I really really want to use this" but you could still use other
host aliases if
it makes sense that the inventory variables override others, the specifics
of a host should override the generalities of the plays.
If a play has remote_user = user1, but some hosts have different users, you
would not be able to use them otherwise, with inventory overriding, this is
possible.
--
On 31 July 2014 00:29, Michael DeHaan wrote:
> OTOH, I see the reasoning of making the play stuff "beat" inventory when
> set as such.
I would have expected that, too, though never used this combo.
Not sure why it's not like this? Brian, are you aware of a reason?
BTW, while I could accept
It has always been the case that inventory 'wins' the only way to override
that is redefining ansible_ssh_user (either as a var or extra_var).
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving
I believe it's intended that the inventory parameter always be used if set.
I'd have to go back through the vast archives to verify the logic, but in
general, usually things work the way they have evolved for concrete
reasons, one of those was being able to set a reasonable default but also
have e
Hi,
I seem to be having issues when remote_user is used in conjunction with
ansible_ssh_user
For this playbook:
- hosts: tag_application_csds tasks:
- command: "whoami" remote_user: deploy
register: whoami
- debug: var=whoami.stdout
with group_vars/tag_application_csds:
