community.general/examples/playbook.yml

---
- hosts: all
  user: root
  vars:
    http_port: 80
    max_clients: 200
  tasks:
  - name: simulate long running op (15 sec), wait for up to 45, poll every 5
    action: command /bin/sleep 15
    async: 45
    poll: 5
  - include: base.yml favcolor=blue
  - name: write the foo config file using vars set above
    action: template src=foo.j2 dest=/etc/some_random_foo.conf
    notify:
    - restart apache
  - name: ensure apache is running
    action: service name=httpd state=started
  - name: pointless test action
    action: command /bin/echo {{ http_port }}
  handlers:
    - include: handlers.yml
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			`---`
Add user to playbook example so it's clear that this is available 2012-03-03 17:02:14 +01:00			`- hosts: all`
			`user: root`
Factoids and push variables via setup are now available to be templated in command args as well as template files. PLUS, variables are now expressed in playbooks without having to know about the setup task, which means playbooks are simpler to read now. 2012-03-06 02:09:03 +01:00			`vars:`
			`http_port: 80`
			`max_clients: 200`
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:`
This adds async poll support to playbooks. See examples. Some more testing due + docs but this is more or less a mirror of what /bin/ansible does. It also has a 'fire and forget' mode if the poll interval is left off or set to 0. 2012-03-13 01:53:10 +01:00			`- name: simulate long running op (15 sec), wait for up to 45, poll every 5`
			`action: command /bin/sleep 15`
			`async: 45`
			`poll: 5`
Parameterized include statements can see top level variables and also be passed specific variables! Code needs cleanup, but works 2012-03-06 04:00:22 +01:00			`- include: base.yml favcolor=blue`
src= parameters for template and copy operations can be relative to the playbook (for /usr/bin/ansible-playbook) or current directory (for /usr/bin/ansible) 2012-03-07 03:13:50 +01:00			`- name: write the foo config file using vars set above`
			`action: template src=foo.j2 dest=/etc/some_random_foo.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`
Factoids and push variables via setup are now available to be templated in command args as well as template files. PLUS, variables are now expressed in playbooks without having to know about the setup task, which means playbooks are simpler to read now. 2012-03-06 02:09:03 +01:00			`- name: pointless test action`
			`action: command /bin/echo {{ http_port }}`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 20:42:41 +01:00			`handlers:`
Ability to import task lists and handler lists from a top level playbook file. It is possible to use multiple import statements to implement 'class' like behavior, and also to share a common list of handlers between multiple patterns. 2012-03-03 16:53:15 +01:00			`- include: handlers.yml`