mirror of https://github.com/ansible/ansible.git
Mirror of https://github.com/ansible/ansible.git
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
10a8c6bc25
* First pass at include_role tests * Reorganize test structure Do all import and include tests in a single target. * Build out more tests and test with linear and free strategy for each type * import_role tests * Set target host for play test * Basic import_playbook tests * Basic import/include_tasks tests * Add recursion test * import_playbook tests * Add import_playbook group_vars test Issue #33177 * Additional group_var tests for import_playbook * Enable recursion test * More work on import_tasks * Run all tests via run.sh, improve conditional tests, add never tag Add never tag to certain failining tests and explicitly skip it for now until #34104 is merged. Some tasks need to remain commented out because they cause the entire play to fail and aren't skippable by tags because they are syntax and/or variable checks. Improve test for whether or not a role was run based on a conditional. Since the [import|include]_role does not register a variable, use a variable that is set inside a role as a canary test for whether or not the role was run. * Use a fail task rather than trigger a failure via bogus command This should resolve the "unstable" test results. * Import tag tests Fix bug it tests where validate tasks weren't run on tag tests. Add tests for task import/include with tags. * Remove test for playbook group_var inheritance |
7 years ago | |
|---|---|---|
| .github | 7 years ago | |
| bin | 7 years ago | |
| contrib | 7 years ago | |
| docs | 7 years ago | |
| examples | 7 years ago | |
| hacking | 7 years ago | |
| lib/ansible | 7 years ago | |
| licenses | 7 years ago | |
| packaging | 7 years ago | |
| test | 7 years ago | |
| ticket_stubs | 7 years ago | |
| .coveragerc | 8 years ago | |
| .gitattributes | 8 years ago | |
| .gitignore | 7 years ago | |
| .gitmodules | 8 years ago | |
| .mailmap | 7 years ago | |
| .yamllint | 7 years ago | |
| CHANGELOG.md | 7 years ago | |
| CODING_GUIDELINES.md | 7 years ago | |
| CONTRIBUTING.md | 7 years ago | |
| COPYING | 13 years ago | |
| MANIFEST.in | 7 years ago | |
| MODULE_GUIDELINES.md | 7 years ago | |
| Makefile | 7 years ago | |
| README.md | 7 years ago | |
| RELEASES.txt | 7 years ago | |
| ROADMAP.rst | 7 years ago | |
| VERSION | 7 years ago | |
| ansible-core-sitemap.xml | 8 years ago | |
| docsite_requirements.txt | 8 years ago | |
| requirements.txt | 8 years ago | |
| setup.py | 7 years ago | |
| shippable.yml | 7 years ago | |
| tox.ini | 7 years ago | |
README.md
Ansible
Ansible is a radically simple IT automation system. It handles configuration-management, application deployment, cloud provisioning, ad-hoc task-execution, and multinode orchestration - including trivializing things like zero downtime rolling updates with load balancers.
Read the documentation and more at https://ansible.com/
You can find installation instructions here for a variety of platforms. Most users should probably install a released version of Ansible from pip, a package manager or our release repository. Officially supported builds of Ansible are also available. Some power users run directly from the development branch - while significant efforts are made to ensure that devel is reasonably stable, you're more likely to encounter breaking changes when running Ansible this way.
Design Principles
- Have a dead simple setup process and a minimal learning curve
- Manage machines very quickly and in parallel
- Avoid custom-agents and additional open ports, be agentless by leveraging the existing SSH daemon
- Describe infrastructure in a language that is both machine and human friendly
- Focus on security and easy auditability/review/rewriting of content
- Manage new remote machines instantly, without bootstrapping any software
- Allow module development in any dynamic language, not just Python
- Be usable as non-root
- Be the easiest IT automation system to use, ever.
Get Involved
- Read Community Information 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.
- All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use
git rebasevsgit mergefor 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. - Users list: ansible-project
- Development list: ansible-devel
- Announcement list: ansible-announce - read only
- irc.freenode.net: #ansible
Branch Info
- Releases are named after Led Zeppelin songs. (Releases prior to 2.0 were 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 Community Information for notes on how to get started.
Authors
Ansible was created by Michael DeHaan (michael.dehaan/gmail/com) and has contributions from over 1000 users (and growing). Thanks everyone!
Ansible is sponsored by Ansible, Inc
License
GNU General Public License v3.0
See COPYING to see the full text.