Go to file
Kent Frazier 3316b87059 Keep ansible-playbook from bombing without extra-vars
A recent change to ansible-playbook to support json extra-vars
also inadvertently broke the script when no extra-vars are
provided. Simply checking to make sure it is defined and truthy
should take care of the issue.
2013-05-31 22:37:16 -05:00
bin Keep ansible-playbook from bombing without extra-vars 2013-05-31 22:37:16 -05:00
docs/man Merge pull request #3040 from bfabio/devel 2013-05-31 13:06:05 -07:00
docsite Add an example of JSON extra variables on the command line. 2013-05-31 16:07:40 -04:00
examples Add version added field to notification modules. 2013-05-11 16:36:37 -04:00
hacking Escape args injected in new style modules 2013-05-24 01:01:07 +02:00
lib/ansible Make the actual user used for executing play available as 'ansible_ssh_user' variable 2013-05-31 16:03:56 -04:00
library Merge pull request #3083 from mvo5/feature/facts-add-statvfs 2013-05-31 14:22:58 -07:00
packaging Added optional dependencies for fireball mode to PKGBUILD. 2013-05-31 12:53:52 -04:00
plugins Update vagrant external inventory file to handle multiple boxes, and --list and --host params. 2013-05-30 14:16:58 +10:00
test Handle '#' in var strings by splitting on ' #' 2013-05-31 12:34:45 -06:00
.gitignore Ignore Intellij IML files. 2013-05-23 09:11:38 +10:00
CHANGELOG.md Update changelog 2013-05-31 16:08:29 -04:00
CONTRIBUTING.md Add a line about testing. 2013-02-23 12:41:00 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Not sure why RPM was trying to avoid certain files starting with f. Change that. 2013-05-29 14:21:25 -04:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md Update README.md 2013-04-06 17:22:21 -03:00
RELEASES.txt Update the release date & code names in the releases file. 2013-04-20 18:21:25 -04:00
setup.py fix package mentioned twice in setup.py 2013-05-15 21:02:53 +02:00
VERSION Update release version. 2013-04-02 20:48:30 -04:00

Ansible

Ansible is a radically simple configuration-management, deployment, task-execution, and multinode orchestration framework.

Read the documentation and more at http://ansible.cc

Many users run straight from the development branch (it's generally fine to do so), but you might also wish to consume a release. You can find instructions on http://ansible.cc/docs/gettingstarted.html for a variety of platforms. If you want a tarball of the last release, go to http://ansible.cc/releases/ and you can also install with pip (though that will bring in some optional binary dependencies you normally do not need).

Design Principles

  • Dead simple setup
  • Super fast & parallel by default
  • No server or client daemons; use existing SSHd
  • No additional software required on client boxes
  • Modules can be written in ANY language
  • Awesome API for creating very powerful distributed scripts
  • Be usable as non-root
  • The easiest config management system to use, ever.

Get Involved

Branch Info

  • Releases are named after Van Halen songs.
  • The devel branch corresponds to the release actively under development.
  • Various release-X.Y branches exist for previous releases
  • We'd love to have your contributions, read "CONTRIBUTING.md" for process notes.

Author

Michael DeHaan -- michael@ansibleworks.com

AnsibleWorks