community.general/examples/playbook.yml

- pattern: '*'
  hosts: /etc/ansible/hosts
  tasks:
  - do:
    - configure template & module variables for future template calls
    - setup a=2 b=3 c=4
  - do:
    - copy a file from the local disk to the remote
    - copy src=/srv/a dest=/srv/b
    notify: 
    - restart apache
  - do:
    - template from local file template.j2 to remote location /srv/file.out
    - template src=/srv/template.j2 dest=/srv/file.out
    notify:
    - restart apache
    - quack like a duck
  - do:
    - if running as non-root whne you template, you should specify the MD file (1)
    - setup a=3 b=4 c=5 metadata=/tmp/metadata.json 
  - do:
    - if running as non-root when you template, you should specify the MD file (2)
    - template src=/srv/template.j2 dest=/srv/file2.out metadata=/tmp/metadata.json
  - do:
    - call something that will fail just to demo failure counts and such
    - 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 06:02:24 +00:00			`- pattern: '*'`
Fixed up KV munging in runner, misc fixes to copy, setup, and template modules 2012-02-27 00:55:26 +00: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 04:54:16 +00: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 08:25:09 +00:00			`- do:`
make copy & template module take key/value parameters so we're consistent. Only the command module works differently now starter manpage for modules allow template file location to be passed into template & setup modules 2012-02-27 00:21:44 +00:00			`- configure template & module variables for future template calls`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 18:05:09 +00:00			`- setup a=2 b=3 c=4`
Compress the playbook format for readability 2012-02-05 17:52:07 +00:00			`- do:`
make copy & template module take key/value parameters so we're consistent. Only the command module works differently now starter manpage for modules allow template file location to be passed into template & setup modules 2012-02-27 00:21:44 +00:00			`- copy a file from the local disk to the remote`
			`- copy src=/srv/a dest=/srv/b`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 19:42:41 +00:00			`notify:`
			`- restart apache`
Added stub for template execution, WIP. 2012-02-24 08:45:36 +00:00			`- do:`
			`- template from local file template.j2 to remote location /srv/file.out`
make copy & template module take key/value parameters so we're consistent. Only the command module works differently now starter manpage for modules allow template file location to be passed into template & setup modules 2012-02-27 00:21:44 +00:00			`- template src=/srv/template.j2 dest=/srv/file.out`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 19:42:41 +00:00			`notify:`
			`- restart apache`
			`- quack like a duck`
Update reporting on playbook runs. 2012-02-25 20:21:11 +00:00			`- do:`
make copy & template module take key/value parameters so we're consistent. Only the command module works differently now starter manpage for modules allow template file location to be passed into template & setup modules 2012-02-27 00:21:44 +00:00			`- if running as non-root whne you template, you should specify the MD file (1)`
			`- setup a=3 b=4 c=5 metadata=/tmp/metadata.json`
			`- do:`
			`- if running as non-root when you template, you should specify the MD file (2)`
			`- template src=/srv/template.j2 dest=/srv/file2.out metadata=/tmp/metadata.json`
			`- do:`
			`- call something that will fail just to demo failure counts and such`
Update reporting on playbook runs. 2012-02-25 20:21:11 +00:00			`- command /bin/false`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 19:42:41 +00: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-24 04:54:16 +00: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 06:02:24 +00: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-26 01:27:11 +00: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-24 04:54:16 +00:00			`- do:`
Notifable handlers only run when something is changed. Awesome. 2012-02-25 19:42:41 +00:00			`- quack like a duck`
			`- command /bin/true`