community.general/examples/playbook.yml

- pattern: '*'
  tasks:
  - do:
    - configure template & module variables
    - setup a=2 b=3 c=4
  - do:
    - copy a file
    - copy /srv/a /srv/b
  - do:
    - template from local file template.j2 to remote location /srv/file.out
    - template /srv/template.j2 /srv/file.out
  - do:
    - update apache
    - command /usr/bin/yum update apache
    onchange:
    - do:
      - restart apache
      - command /sbin/service apache restart
    - do:
      - run bin false
      - command /bin/false
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: '*'`
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:`
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 09:25:09 +01:00			`- do:`
			`- configure template & module variables`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 19:05:09 +01:00			`- setup a=2 b=3 c=4`
Compress the playbook format for readability 2012-02-05 18:52:07 +01:00			`- do:`
			`- copy a file`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 19:05:09 +01:00			`- copy /srv/a /srv/b`
Added stub for template execution, WIP. 2012-02-24 09:45:36 +01: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 19:05:09 +01:00			`- template /srv/template.j2 /srv/file.out`
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			`- 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 07:02:24 +01:00			`- update apache`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 19:05:09 +01:00			`- command /usr/bin/yum update apache`
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			`onchange:`
			`- 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 07:02:24 +01:00			`- restart apache`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 19:05:09 +01:00			`- command /sbin/service apache restart`
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			`- do:`
			`- run bin false`
Can it get an easier? Yes it can! Further simply playbook format. 2012-02-05 19:05:09 +01:00			`- command /bin/false`
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