community.general/examples/playbook.yml

- pattern: '*'
  hosts: '/etc/ansible/hosts'
  tasks:
  - do:
    - configure template & module variables
    - setup a=2 b=3 c=4
  - do:
    - copy a file
    - copy /srv/a /srv/b
    notify: 
    - restart apache
  - do:
    - template from local file template.j2 to remote location /srv/file.out
    - template /srv/template.j2 /srv/file.out
    notify:
    - restart apache
    - quack like a duck
  - do:
    - something that will fail
    - command /bin/false
  handlers:
    - do:
      - restart apache
      - service name=httpd ensure=restarted
    - do:
      - quack like a duck
      - command /bin/true
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 01:02:24 -05:00			`- pattern: '*'`
Add optional hosts parameter to examples to show how we can override the host file in a playbook to load different groups of hosts. 2012-02-25 19:56:06 -05: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-23 23:54:16 -05:00			`tasks:`
Added a setup module which can be used to place key-value JSON data on the system for use in a later template module. These values could also be used for module-specific config. 2012-02-24 03:25:09 -05:00			`- do:`
			`- configure template & module variables`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 13:05:09 -05:00			`- setup a=2 b=3 c=4`
Compress the playbook format for readability 2012-02-05 12:52:07 -05:00			`- do:`
			`- copy a file`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 13:05:09 -05:00			`- copy /srv/a /srv/b`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 14:42:41 -05:00			`notify:`
			`- restart apache`
Added stub for template execution, WIP. 2012-02-24 03:45:36 -05:00			`- do:`
			`- template from local file template.j2 to remote location /srv/file.out`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 13:05:09 -05:00			`- template /srv/template.j2 /srv/file.out`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 14:42:41 -05:00			`notify:`
			`- restart apache`
			`- quack like a duck`
Update reporting on playbook runs. 2012-02-25 15:21:11 -05:00			`- do:`
			`- something that will fail`
			`- command /bin/false`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 14:42:41 -05:00			`handlers:`
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-23 23:54:16 -05:00			`- do:`
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 01:02:24 -05:00			`- restart apache`
A basic service module with 'ensure' idempotence semantics. Playbook updated to use service module vs command module for restarting. May be some bugs and requires the service to implement 'status' -- and probably some better error handling (i.e. return JSON with "failed" element if failed). Improvements welcome. 2012-02-25 20:27:11 -05:00			`- service name=httpd ensure=restarted`
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-23 23:54:16 -05:00			`- do:`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 14:42:41 -05:00			`- quack like a duck`
			`- command /bin/true`