+1 here; having ansible-playbook return a 0 exit code when tasks fail make
automating with a CI server more difficult then it has to be.
On Friday, January 10, 2014 at 11:01:36 AM UTC-8, Mike Bain wrote:
>
> +1 Having an option for ansible to return an exit code if a task fails
> would be good f
It is being include in a group_var for the hosts, is there a better way to
do this?
On Tuesday, October 18, 2016 at 10:39:00 AM UTC-7, Matt Davis wrote:
>
> Where are you setting the connection types to winrm then?
>
> On Tuesday, October 18, 2016 at 10:26:18 AM UTC-7, Stephe
I'm not sure how. Can you provide a complete working example? My inventory
file is pretty straight forward. My inventory looks like this
[box1]
ip.address
[box2]
another.ip.address
[alpha:children]
ip.address
[beta:children]
another.ip.address
[somewindowshosts]
alpha
beta
--
You received
It seems that it is impossible to run a local task when talking to windows
hosts. This is pretty much a show stopper for my current use case of
Ansbile.
ansible version: ansible 2.1.1.0
using any of the following, all result in the same error
- name: deploy some stuff
hosts: somewindowshos
