community.general/examples/playbook.yml

---
- pattern: '*'
  hosts: /etc/ansible/hosts
  tasks:
  - name: config step
    action: setup a=2 b=3 c=4
  - name: copy comand
    action: copy src=/srv/a dest=/srv/b
    notify: 
    - restart apache
  - name: template step
    action: template src=/srv/template.j2 dest=/srv/file.out
    notify:
    - restart apache
  - name: execute bin false
    comment: call something that will fail just to demo failure counts and such
    action: command /bin/false
  - name: execute bin true
    comment: this will never be executed because previous will fail
    action: command /bin/true
  handlers:
    - name: restart apache
      action: service name=httpd state=restarted
Update man pages. Fix formatting in playbook example. Also, YAML documents by definition start with '---', so I have added this to the example and the manpage 2012-02-27 03:09:56 +01:00			`---`
Added rough sketch of what I want for playbook support. Debug heavy at the moment as I figure out how logging/output might look. A couple of major TODO features also listed in the file. 2012-02-24 07:02:24 +01:00			`- pattern: '*'`
Fixed up KV munging in runner, misc fixes to copy, setup, and template modules 2012-02-27 01:55:26 +01:00			`hosts: /etc/ansible/hosts`
We don't have modules that list when things change just yet. I plan to handle this by having a changed=True/False in the JSON for these modules. Added a note so folks won't think we can only execute shell :) 2012-02-24 05:54:16 +01:00			`tasks:`
Drastically simply playbook syntax 2012-02-27 02:54:51 +01:00			`- name: config step`
			`action: setup a=2 b=3 c=4`
			`- name: copy comand`
			`action: copy src=/srv/a dest=/srv/b`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 20:42:41 +01:00			`notify:`
			`- restart apache`
Drastically simply playbook syntax 2012-02-27 02:54:51 +01:00			`- name: template step`
			`action: template src=/srv/template.j2 dest=/srv/file.out`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 20:42:41 +01:00			`notify:`
			`- restart apache`
Drastically simply playbook syntax 2012-02-27 02:54:51 +01:00			`- name: execute bin false`
			`comment: call something that will fail just to demo failure counts and such`
			`action: command /bin/false`
Stop evaluating a host in a playbook when it encounters the first failure. 2012-02-28 04:28:01 +01:00			`- name: execute bin true`
			`comment: this will never be executed because previous will fail`
			`action: command /bin/true`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 20:42:41 +01:00			`handlers:`
Drastically simply playbook syntax 2012-02-27 02:54:51 +01:00			`- name: restart apache`
Rename 'ensure' to 'state' because I think it's a bit cleaner and doesn't imply all modules take a common parameter name. But more or less we still work idempotently in modules. 2012-02-27 04:31:42 +01:00			`action: service name=httpd state=restarted`