1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Find a file
James Cammarata e36a8d466e Don't re-query inventory when trimming failed/dark hosts
Since the filter list contains hosts, passing that back to list_hosts()
in the inventoy causes issues when the hostname is an IPv6 address
(with :'s interpreted as group unions). Since we already have the list
of hosts, we should not need to pass that back through inventory a
second time.

Fixes #7446
2014-05-20 14:58:37 -05:00
bin Commenting out pkg_resources lines for now, as they break hacking/env-setup 2014-04-29 15:24:00 -05:00
docs/man Fix typos in ansible-playbook man page source 2014-04-14 01:22:18 +03:00
docsite Add missing space between var and delimeter 2014-05-17 16:43:23 +03:00
examples Adding a new system_warnings config option to supress warnings 2014-04-30 14:44:10 -05:00
hacking Make test-module interpret --args='{...' as yaml 2014-04-10 21:14:42 +02:00
legacy Various tests using datafiles are being moved into the integration test framework (tests_new right now). 2014-02-20 17:16:58 -05:00
lib/ansible Don't re-query inventory when trimming failed/dark hosts 2014-05-20 14:58:37 -05:00
library Default use_proxy to True for fetch_url() 2014-05-19 23:04:13 -05:00
packaging Synchronize .deb package version with VERSION file 2014-05-07 15:12:08 +02:00
plugins Docker client occasionally returns a NoneType, so we have to catch the TypeError 2014-05-05 10:51:58 -05:00
test Add a broken test that shows extensions not skipped 2014-05-14 23:43:14 -07:00
.gitignore ignore remnants from doing a setup.py install 2014-05-05 13:13:01 -05:00
CHANGELOG.md Update CHANGELOG.md 2014-05-05 17:45:04 -04:00
CODING_GUIDELINES.md Update CODING_GUIDELINES.md 2014-03-14 11:23:34 -05:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-03-31 18:48:28 -04:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Assert the MOCK_CFG exists for the mock-rpm build target 2014-05-09 09:01:44 -04:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md Update README.md 2014-04-03 08:25:26 -04:00
RELEASES.txt Update RELEASES.txt 2014-05-05 17:43:40 -04:00
setup.py Merge pull request #6994 from tonk/docfix 2014-04-29 16:50:00 -04:00
VERSION Version bump for 1.7 2014-05-05 16:37:46 -05:00

PyPI version PyPI downloads

Ansible

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

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

  • Have a dead simple setup process and a minimal learning curve
  • Be super fast & parallel by default
  • Require no server or client daemons; use existing SSHd
  • Use a language that is both machine and human friendly
  • Focus on security and easy auditability/review/rewriting of content
  • Manage remote machines instantly, without bootstrapping
  • 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 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.
  • 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