ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Update README.md

Browse source
This commit is contained in:
Michael DeHaan 2012-03-06 08:54:06 -05:00
parent de3cff8cef
commit 7cb6ce6613
1 changed files with 10 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
README.md
View file

@ -167,9 +167,7 @@ An example showing a small playbook:
max_clients: 200 max_clients: 200
user: root user: root
tasks: tasks:
- include: base.yml - include: base.yml somevar=3 othervar=4
- name: configure template & module variables for future template calls
action: setup http_port=80 max_clients=200
- name: write the apache config file - name: write the apache config file
action: template src=/srv/httpd.j2 dest=/etc/httpd.conf action: template src=/srv/httpd.j2 dest=/etc/httpd.conf
notify: notify:
@ -181,10 +179,15 @@ An example showing a small playbook:
Some key concepts here include: Some key concepts here include:
* Everything is expressed in simple YAML * Everything is expressed in a simple YAML data format, not a custom language, not code.
* Steps can be run as non-root * Playooks can have many steps
* Modules can notify 'handlers' when changes occur. * Any step can run as any user
* Tasks and handlers can be 'included' to faciliate sharing and 'class' like behavior * Conditional handlers fire on 'notify'. Ex: restart apache only once, at the end, only if needed
* Tasks and handlers can be 'included' to faciliate sharing and reuse
* Include statements can take parameters for customization, and be used more than once per file
* Variables from the host system (from facter, ohai, etc) bubble-up for use in templates
* Variables can be deferenced like {{ varname }} in both include directives & templates
* Templates are powered by Jinja2: http://jinja.pocoo.org/docs/templates/#synopsis
To run a playbook: To run a playbook: