Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save marktheunissen/2979474 to your computer and use it in GitHub Desktop.
Save marktheunissen/2979474 to your computer and use it in GitHub Desktop.
Insanely complete Ansible playbook, showing off all the options
This playbook has been removed as it is now very outdated.
Copy link

I just wanted to mention to everyone that this, while great at the time, is now pretty old.

It doesn't show roles and a lot of features in 1.2, and still uses the "only_if" syntax, which is now made easier by "when". In addition, variable substitution is also in many ways improved.

While things remain compatible, these are not the best ways to do everything in all cases. (Many things remain unchanged, of course), nor does it show everything.

I would suggest reading the latest documentation at and then also looking at the "ansible-examples repo:

Which shows various things put into context.

Copy link

mpdehaan is right. For example, the example above (line 50 and following) states ',' as separator when using multiple groups in a hosts declaration, while shows ':' . The latter is correct, took me some time to figure it out.

But still my respect for this of course! It's helped me a lot getting to know all of ansible's possibilities!

Copy link

pfalcon commented Jul 13, 2013

Other misguiding info in this example:

# Notice the minus on the line below -- this starts the playbook's record
# in the YAML document. Only one playbook is allowed per YAML file.  Indent
# the body of the playbook.
- hosts: all

So, only one playbook is allowed per YAML file, actually, such YAML file is a playbook. But playbook consists of one or more of "plays", and "hosts:" line marks beginning of a play, there can be multiple, each applying to a different (or even to same!) set of hosts.

Copy link

Shouldn't this say ${web.httpd} instead of ${web.apache} ?

# For this example, ${web.memcache} and ${web.apache} are both usable
# variables.

Copy link

At this point in time ${foo} variables are deprecated and slated for removal in 1.6.

Operators with "when_foo" are also completely removed as of 1.5 in favor of the simplified when, and there is no "only_if" operation.

While I'm very happy this was created, folks should refer to instead at this time.

Copy link

ranjib commented Feb 1, 2014

this is awesome!

Copy link

1.6 is due for release in about a week.

At this point, I should also mention a lot of things like do/until are not shown here.

$foo variables no longer are also no longer valid syntax in 1.6 (devel branch, releasing very soon)

Please consult for all the latest

Copy link

jtyr commented Nov 30, 2014

This Gist is very useful and I wish the author keeps it up-to-date. If somebody already tried to update it, please place your Gist link here.

Copy link

@mpdehaan while this may be out of date it is still way more informative for the beginner than any of the official examples or docs. Take one of the examples in your example directory: what does this tell someone like me who just picked up ansible?

Copy link

nfarrar commented Jan 30, 2015

Wicked useful, thank you!

Copy link

An insanely great job ;)

Copy link

Nice collection!

Copy link

thomo commented Sep 20, 2015

I just started to learn ansible but would suggest the following modifications:

  • line 83:
    • org

      user: remoteuser
    • new

      remote_user: remoteuser
      ### The remote_user parameter was formerly called just user. It was renamed in Ansible 1.4 to make it more distinguishable from the user module (used to create users on remote systems).
  • line 107:
    • org

       # For this example, ${web.memcache} and ${web.apache} are both usable
    • new

      # For this example, ${web.memcache} and ${web.httpd} are both usable

Copy link

is there a way to specify the become user is handlers part?


  • name: restart apache
    service: name=apache state=restarted

Copy link

ghost commented Mar 14, 2016

I know this is out of date... but I'm going to say it anyways as an FYI-- in Line 433 you can no longer include handlers as of Ansible 2.0

Copy link

This would be really cool to evolve and keep up to date to showcase a detailed changelog.

Copy link

shiplu commented Apr 12, 2016

Great Playbook. A lot of things are clear to me now.

Copy link

gretel commented May 4, 2016

should be part of the core documentation. thanks!

Copy link

SayBeano commented May 23, 2016


edit: And thanks, @marktheunissen!

Copy link

henryxn commented May 26, 2016

In term of using variable in hosts attribute (line 58)

hosts: $groups -- apply to all hosts specified in the variable $groups

hosts : group # No $

$ ansible-playbook playbook1.yml -e "group=myservers"
$ ansible-playbook playbook1.yml --extra-vars="target=myservers"

Copy link

akofink commented Jul 26, 2016

sudo: true is deprecated in favor of become: true


Copy link

which editor u use for yaml?

Copy link

@antoniopinarella you can use any text editor. I use vim for .yml and it works fine.
(Probably you found it out. However for new people searches. )

Copy link

flamein commented Mar 9, 2018

Can we please bury this Gist? it keeps showing up as clickbait in search engines while the syntax is horribly outdated.

Copy link

dataf3l commented Sep 25, 2019

I love this, please include "become"

Copy link

I have made a fork and updated some of the content that has been deprecated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment