Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications — automate in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com/ansible/
Find a file
Jesse Keating 4593e3c357 Make sure requested version tag gets downloaded
There is a subtle bug in how the git module currently works. If the
version you request is a tag name, and you've already got the repo
cloned, and the tag name is a new tag, but refers to the already checked
out working copy, the git module would exit early without change. This
is bad as it means the new tag ref was not fetched and could not be used
in later tasks.

This change will check if the version is a remote tag, and if the tag
doesn't exist locally. If that is true, it'll do a fetch.

The activity could still be seen as not a change, because the working
copy won't be updated, if the new tag refers to the already checked out
copy, but that's not different than before and can be fixed as a more
comprehensive overhaul of tracking change in the git module.
2014-02-07 14:13:04 -08:00
bin More site rename things. 2014-01-28 20:29:42 -05:00
docs/man Add reference to Guru to sidebar. 2014-01-30 12:32:45 -05:00
docsite Updating changelog and docs for the new play_hosts variable 2014-02-06 00:01:39 -05:00
examples Add an issue template 2014-02-04 10:15:08 -05:00
hacking Merge pull request #5461 from sivel/test-module-interpreter 2014-01-29 16:24:37 -08:00
lib/ansible Merge pull request #5880 from willthames/ec2_modules_refactor 2014-02-06 11:08:09 -05:00
library Make sure requested version tag gets downloaded 2014-02-07 14:13:04 -08:00
packaging Make PKGBUILD packaging standards compliant. 2014-02-05 23:40:02 +01:00
plugins reword "except Error as e:" into "except Error, e:" to be compatible with Python 2.5 (#5852) 2014-02-03 13:00:40 -06:00
test Make tmp paths in TestRunner dynamic based on pid 2014-02-05 23:12:31 -06:00
.gitignore Further modifications to the module formatter to adjust to the new theme, and some misc docs text corrections. 2013-12-25 13:24:29 -05:00
CHANGELOG.md Updating changelog and docs for the new play_hosts variable 2014-02-06 00:01:39 -05:00
CODING_GUIDELINES.md Missing colon. 2014-01-26 17:06:32 -05:00
CONTRIBUTING.md AnsibleWorks -> Ansible 2014-01-28 20:29:42 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Remove man3 stuff since this is available via ansible-doc, rpm target should 2014-01-03 11:06:45 -05:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md AnsibleWorks -> Ansible 2014-01-28 20:29:42 -05:00
RELEASES.txt Update RELEASES.txt 2014-01-30 10:31:43 -05:00
setup.py AnsibleWorks -> Ansible 2014-01-28 20:29:42 -05:00
VERSION Version bump for 1.5 2013-11-21 16:33:23 -05:00

PyPI version

Ansible

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

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

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 here for a variety of platforms. If you want a tarball of the last release, go to releases.ansible.com and you can also install with pip.

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

  • Read Contributing.md for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
  • When submitting a bug report, include 1) the output of 'ansible --version', 2) what you expected to happen, 3) what actually happened, and 4) any relevant commands and output.
  • All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use "git rebase" vs "git merge" for this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed.
  • irc.freenode.net: #ansible

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@ansible.com

Ansible, Inc