mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
672794f586
A first stab at a pull-based model for ansible. This does two things: 1. Invoke the git module via Runner to set up a git repository on the localhost. It sets up Runner to use transport='local' and forces the inventory to just 'localhost'. 2. Run any playbooks provided. By default, this wants to run the playbook local.yml. This also sets transport='local' and sets the host_list to a list: localhost, fqdn, and hostname. The reason for setting the host_list and not using override_hosts is because there may be plays in the playbook that are not meant for a specific host. That is, if the git repository is for the entire site and not host-specific, you don't want to override hosts and apply all plays to any given host. This has the downside of potentially running a play three times if the play is defined for 'hosts: all'. |
||
---|---|---|
bin | ||
docs/man | ||
examples | ||
hacking | ||
lib/ansible | ||
library | ||
packaging | ||
test | ||
.gitignore | ||
CHANGELOG.md | ||
COPYING | ||
Makefile | ||
MANIFEST.in | ||
README.md | ||
setup.py | ||
VERSION |
Ansible
Ansible is a radically simple configuration-management, deployment, task-execution, and multinode orchestration framework.
Read all about at it at (http://ansible.github.com)
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
- ansible-project mailing list
- irc.freenode.net: #ansible
Branch Info
- The master branch corresponds to release 0.3 "Baluchitherium".
- Bug fixes WILL be periodically made to the master branch.
- The devel branch corresponds to release 0.4 "Unchained".
- Note: sudo support works much better in 0.4/devel, consider trying it.
- See CHANGELOG.md for release notes to track each release.
Patch Instructions
Contributions to the core and modules are greatly welcome.
- Required Process:
- Submit github pull requests to the "ansible/devel" branch for features
- Fixes for bugs may be submitted to "ansible/master"
- Make sure "make tests" passes before submitting any requests.
- Bonus points:
- Joining the mailing list
- Using squash merges
- Updating the "rst/*" files in the docs project and "docs/" manpage content
- Adding more unit tests
- Avoid:
- Sending patches to the mailing list directly.
- Sending feature pull requests to the 'master' branch instead of the devel branch
- Sending pull requests to mpdehaan's personal ansible fork.
Author
Michael DeHaan -- michael.dehaan@gmail.com