cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
8538 commits 47 branches 390 tags 440 MiB
Python 88.4%
PowerShell 7.5%
Shell 2%
C# 1.9%
Makefile 0.1%
Find a file
Richard C Isaacson a3261500dd Addresses #5739 and cleans up copy.py 
The copy action_plugin is not easy to read. Part of this commit is taking that file, restructuring it, and adding comments. No functionality changed in how it interacts with the world.

The fix for #5739 ends up being the assumption that there is a cleanup 'rm -rf' that happens at the end of the copy loop. This was not the fact before and we made a bunch of tmp directories that we hoped would end up being cleaned up. Now we just use the tmp directory that the runner provides and cleanup inline if it is a single file to be coppied or after the loop if it is a recursive copy.

As a part of this we did end up having to change runner to provide a flag so that we could short the inline tmp directory removal. This flag defaults to True so it will not change the behavior of other modules that are being called.
2014-02-04 12:44:10 -06: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 Merge pull request #5716 from kintamanimatt/playbook-roles-badparagraph 2014-02-03 09:00:16 -08:00
examples AnsibleWorks -> Ansible 2014-01-28 20:29:42 -05:00
hacking Merge pull request #5461 from sivel/test-module-interpreter 2014-01-29 16:24:37 -08:00
lib/ansible Addresses #5739 and cleans up copy.py 2014-02-04 12:44:10 -06:00
library 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
packaging AnsibleWorks -> Ansible 2014-01-28 20:29:42 -05: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 Merge pull request #5337 from bob-smith/bugfixFQDNParsing 2014-01-14 08:28:38 -08: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 Adding no_log: capability for tasks 2014-01-31 16:58:46 -06: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

README.md

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