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.
 
 
 
 
 
Go to file
Justin Mayer fda131504b Support multiple vault passwords in keyring script
Allows users to specify a key name in a given project’s `ansible.cfg`
file and thus handle keyring integration with vaults with different
passwords. If no key name is specified, the original default `ansible`
key name will be used.

Other improvements:

* `username` is now optional; defaults to user that invokes the script
* change string interpolation to new `.format()` style
* clean up and expand upon documentation
* enforce PEP 8 compliance
8 years ago
.github Remove the hint to report module issue elsewhere. 8 years ago
bin errors to stderr 8 years ago
contrib Support multiple vault passwords in keyring script 8 years ago
docs become options dont qualify as new anymore 8 years ago
examples Add missing support for -CertValidityDays (#21009) 8 years ago
hacking Legacy pep8 clean fixes for contrib and hacking (#21081) 8 years ago
lib/ansible Restore "skipping: no hosts matched" message 8 years ago
packaging Updating packaging releases 8 years ago
test Convert unit test yield to pytest parametrize. 8 years ago
ticket_stubs Remove obsolete ticket stubs. 8 years ago
.coveragerc Update coverage exclusions. (#18675) 8 years ago
.gitattributes updated changelog with 1.8.2-4 content, added .gitattributes 10 years ago
.gitignore Enable more `ios` tests on Shippable. 8 years ago
.gitmodules Code cleanup. 8 years ago
.mailmap Add new mailmap entry for @willthames 8 years ago
.yamllint Lint YAML files under test/ 8 years ago
CHANGELOG.md Add 2.3.0 entries for module_utils via pluginloader, selectors, and py3 (#21019) 8 years ago
CODING_GUIDELINES.md Migrate basestring to a python3 compatible type (#17199) 8 years ago
CONTRIBUTING.md Update CONTRIBUTING.md with more recent developments 9 years ago
COPYING license file should be in source tree 13 years ago
MANIFEST.in include all docs and tests in the sdist (#20004) 8 years ago
MODULE_GUIDELINES.md Move GUIDELINES.md from modules repo (#19313) 8 years ago
Makefile remove coverage files on clean 8 years ago
README.md Remove obsolete files and instructions. (#19079) 8 years ago
RELEASES.txt brought releases up to date 8 years ago
ROADMAP.rst Update ROADMAP (#20002) 8 years ago
VERSION Bumping devel version to 2.3.0 8 years ago
ansible-core-sitemap.xml Remove remnants of obsolete fireball mode. 8 years ago
setup.py Move ssh and local connection plugins from using raw select to selectors 8 years ago
shippable.yml Temporarily remove FreeBSD 11.0 from CI. 8 years ago
tox.ini Update tox.ini to match current standards 8 years ago

README.md

PyPI version Build Status

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/

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 to download a tarball of a release, go to releases.ansible.com, though most users use yum (using the EPEL instructions linked above), apt (using the PPA instructions linked above), or pip install ansible.

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 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.
  • 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.
  • For releases 1.8 - 2.2, modules are kept in different repos, you'll want to follow core and extras
  • 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

Licence

GNU Click on the Link to see the full text.