rds,
> Vinod Kumar
>
>
> On Wednesday, 30 August 2017 18:57:26 UTC+5:30, N. Bailey wrote:
>
>> Hi Vinod,
>>
>> I don't quite understand your use case - only the Ansible version on the
>> controller that you run the playbook from matters; Ansible runs co
Hi Ansible list,
I'm thinking my way through a solution to loop through a set of hosts and
run a playbook against them one at a time. If the playbook had only one
play in it that'd be easy:
- name: Do something against a few hosts at a time.
hosts: target-hosts
serial: 2
Hi Vinod,
I don't quite understand your use case - only the Ansible version on the
controller that you run the playbook from matters; Ansible runs commands by
SSH on the nodes you manage with it, and at that point sends them
executable scripts that don't need any Ansible-specific packages
eGenerator) but it would
> of course only be compatible with nodes running Powershell V5.
>
>
> On Wednesday, August 17, 2016 at 11:34:55 AM UTC+2, N. Bailey wrote:
>>
>> Hi ansible-devel,
>>
>> Quick question for anyone running Ansible on Windows: has anyone used
we can definetely add
> that. Now with all the various psv5 version numbers out there that might
> actually be a very good idea.
>
> On Monday, August 8, 2016 at 3:49:38 PM UTC+2, N. Bailey wrote:
>>
>> Your guess is right, there's no converting to JSON needed. The
>>
Your guess is right, there's no converting to JSON needed. The
ansible_psversion variable below is just the output of a plain `
$PSVersionTable.PSVersion`, and the module splits it nicely for me:
```
"ansible_powershell_version": 4,
*"ansible_psversion": {*
*"Build":
