From 7cb6ce66138a0bed27f257d94eedca37a54660a6 Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Tue, 6 Mar 2012 08:54:06 -0500 Subject: [PATCH] Update README.md --- README.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index db3bfa2990..5d0f49c1c9 100644 --- a/README.md +++ b/README.md @@ -167,9 +167,7 @@ An example showing a small playbook: max_clients: 200 user: root tasks: - - include: base.yml - - name: configure template & module variables for future template calls - action: setup http_port=80 max_clients=200 + - include: base.yml somevar=3 othervar=4 - name: write the apache config file action: template src=/srv/httpd.j2 dest=/etc/httpd.conf notify: @@ -181,10 +179,15 @@ An example showing a small playbook: Some key concepts here include: - * Everything is expressed in simple YAML - * Steps can be run as non-root - * Modules can notify 'handlers' when changes occur. - * Tasks and handlers can be 'included' to faciliate sharing and 'class' like behavior + * Everything is expressed in a simple YAML data format, not a custom language, not code. + * Playooks can have many steps + * Any step can run as any user + * 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: