Windows: Do not re-use ansible_ssh_user (etc) variable names for WinRM connections

Archives Ansible Developer
1

Hello,

I am feeling some pain with Windows WinRM connections re-using a variable name that’s A.) inaccurate and B.) shared with SSH connections for linux.

Reference docs: http://docs.ansible.com/intro_windows.html

Re-using this variable name for Windows connections means that you have to have a group_vars entry for Windows and it has to be placed (nested) within your inventory in such a way that it won’t get stomped by the (appropriately named) ansible_ssh_user/password variables.

The docs make this seem like a non-issue but in a logical inventory design this becomes cumbersome:

(Example inventory)

2

Good points, and I couldn’t agree more. The vars should reflect that they’r winrm and not ssh connections. Anyone care to PR this?

3

Actually I was thinking of a more general set of variables:

ansible_conn_user
ansible_conn_pass
ansible_conn_port
ansible_conn_key (this also works for client certs)
ansible_conn_host
ansible_conn_proxy
ansible_connection

Which still would still require 'per connection type' groups