community.general/examples/playbook.yml

---
- hosts: '*'
  tasks:
  - name: configure template & module variables for future template calls
    action: setup http_port=80 max_clients=200
  - name: write the apache config file
    action: template src=/srv/httpd.j2 dest=/etc/httpd/conf
    notify:
    - restart apache
  - name: ensure apache is running
    action: service name=httpd state=started
  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			`---`
rename 'pattern' to 'hosts' in playbook format. 2012-03-02 04:20:45 +01:00			`- 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:`
update playbook docs with updated syntax / minor edits 2012-02-28 04:48:45 +01:00			`- name: configure template & module variables for future template calls`
			`action: setup http_port=80 max_clients=200`
			`- name: write the apache config file`
			`action: template src=/srv/httpd.j2 dest=/etc/httpd/conf`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 20:42:41 +01:00			`notify:`
			`- restart apache`
update playbook docs with updated syntax / minor edits 2012-02-28 04:48:45 +01:00			`- name: ensure apache is running`
			`action: service name=httpd state=started`
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`
update playbook docs with updated syntax / minor edits 2012-02-28 04:48:45 +01:00			`- action: service name=httpd state=restarted`