Re: [ansible-devel] Re: Playbook help - syntax

2016-05-25 Thread 'jhawkesworth' via Ansible Development
Kai, Thanks for this, I didn't know that should make converting ad hoc ansible command into playbook style entries easier. Stylistically I wouldn't want to mix key: value and key=value though as in the example above. Jon On Wednesday, May 25, 2016 at 9:52:30 AM UTC+1, Kai Stian Olstad wrote: >

Re: [ansible-devel] Re: Playbook help - syntax

2016-05-25 Thread Kai Stian Olstad
On 25.05.2016 07:23, 'jhawkesworth' via Ansible Development wrote: Single line ansible module calls can use the key=value key=value syntax, but when you are using the multi-line yaml style syntax it needs to be key: value This statement is not correct. yamllint.com or a yaml-aware text edit

[ansible-devel] Re: Playbook help - syntax

2016-05-24 Thread 'jhawkesworth' via Ansible Development
Yes, Will is right, this is really a question for ansible-project. However, it looks to me like you have an = where there should be a : in log_path= "c:/temp/ansible_wu.txt" should be log_path: "C:/temp/ansible_wu.txt" Single line ansible module calls can use the key=value key=value synt

[ansible-devel] Re: Playbook help - syntax

2016-05-24 Thread Will Thames
This is a question for the ansible-project list rather than ansible-devel. The playbook you've posted doesn't appear complete, as the error message relates to a task name that isn't in the below playbook (this is feedback so that you can have better luck in ansible-project) On Wednesday, May 25