ansible/examples/playbooks/tasks/base.yml

---

# this is the example of an included tasks file.  It contains a flat list of tasks
# they can notify other tasks, and have full access to variables from 'vars'
# or 'vars_files' directives.  Further, if ohai or facter were installed on 
# the remote machines, variables from those tools can be accessed on the 'action'
# line or in templates.  Just prefix with 'facter_' or 'ohai_' before the particular
# variable.

# possible uses for a included yaml file might be to represent a 'class' of a system
# like defining what makes up a webserver, or you might have a common 'base.yml'
# (like this) that might be applied to all your systems as well.

- name: no selinux
  action: command /usr/sbin/setenforce 0

- name: no iptables
  action: service name=iptables state=stopped

- name: made up task just to show variables work here
  action: command /bin/echo release is $release
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. 13 years ago			`---`
Annotate more files, fix missing imports messing with playbooks. Hey Tim, please test your stuff :) 13 years ago
			`# this is the example of an included tasks file. It contains a flat list of tasks`
			`# they can notify other tasks, and have full access to variables from 'vars'`
			`# or 'vars_files' directives. Further, if ohai or facter were installed on`
			`# the remote machines, variables from those tools can be accessed on the 'action'`
			`# line or in templates. Just prefix with 'facter_' or 'ohai_' before the particular`
			`# variable.`

			`# possible uses for a included yaml file might be to represent a 'class' of a system`
			`# like defining what makes up a webserver, or you might have a common 'base.yml'`
			`# (like this) that might be applied to all your systems as well.`

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. 13 years ago			`- name: no selinux`
			`action: command /usr/sbin/setenforce 0`
Annotate more files, fix missing imports messing with playbooks. Hey Tim, please test your stuff :) 13 years ago
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. 13 years ago			`- name: no iptables`
			`action: service name=iptables state=stopped`
Annotate more files, fix missing imports messing with playbooks. Hey Tim, please test your stuff :) 13 years ago
			`- name: made up task just to show variables work here`
Allow groups to be passed to runner API to make parse_hosts optional, misc fixes as a result of refactoring in Runner. Cleanup in Playbooks module is next. 13 years ago			`action: command /bin/echo release is $release`
Annotate more files, fix missing imports messing with playbooks. Hey Tim, please test your stuff :) 13 years ago