No description
Find a file
Toshio Kuratomi b8279e7447 Only change to short IDs for delete (#5353)
* Only change to short IDs for delete

If the user specifies long IDs, use them for all commands except for
deleting a key.  Need to use short IDs there because of an upstream
apt_key bug.  Fixed in apt_key 1.10 (fix is present in Ubuntu 16.04 but
not Ubuntu 14.0 or some Debians).

Fixes #5237

* Check that apt-key really erased the key

When erasing a key, apt-key does not understand how to process subkeys.
This update explicitly checks that the key_id is no longer present and
throws an error if it is.  It also hints at subkeys being a possible
problem in the error message and the documentation.

Fixes #5119

* Fix apt_key check mode with long ids

apt-key can be given a key id longer than 16 chars to more accurately
define what key to download.  However, we can use a maximum of 16
chars to verify whether a key is installed or not.  So we need to use
different lengths for the id depending on what we're doing with it.

Fixes #2622

Also:

* Some style cleanups
* Use get_bin_path to find the path to apt-key and then use that when
  invoking apt-key
* Return a nice user error message if the key was not found on the
  keyserver
* Make file and keyring parameters type='path' so envars and tilde are
  expanded
2016-12-08 11:25:23 -05:00
.github
bin functional updates to ansible-connection (#18574) 2016-11-30 16:26:49 -05:00
contrib Fix auth in collins.py inventory 2016-11-23 14:39:25 -05:00
docs/man Update ansible.1.asciidoc.in (#18464) 2016-11-11 08:58:19 -05:00
docs-api
docsite Fix minor typo in roles doc (#18740) 2016-12-04 16:11:46 -08:00
examples change to ~ instead of $HOME to avoid undefined (#18551) 2016-11-21 07:31:50 -08:00
hacking Update the metadata tool (#18765) 2016-12-06 06:27:10 -08:00
lib/ansible Only change to short IDs for delete (#5353) 2016-12-08 11:25:23 -05:00
packaging Updating release versions for release playbook 2016-11-04 14:27:08 -05:00
test add back reverted change to network_cli (#18761) 2016-12-05 21:42:09 -05:00
ticket_stubs Add ticket stub with info on reporting locale info (#16310) 2016-11-28 02:01:28 -08:00
.coveragerc Update coverage exclusions. (#18675) 2016-11-29 22:46:56 -08:00
.gitattributes
.gitignore Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
.gitmodules removed core and extras submodules 2016-12-07 15:44:53 -05:00
.mailmap
.yamllint Lint YAML files under test/ 2016-11-11 14:50:57 -08:00
ansible-core-sitemap.xml
CHANGELOG.md ansible_playbook_python (#18530) 2016-11-23 16:30:46 -05:00
CODING_GUIDELINES.md
CONTRIBUTING.md
COPYING
Makefile Clean up shebangs for various files. 2016-11-02 17:00:27 -07:00
MANIFEST.in
README.md Add link to licence file (COPYING) in README (#18521) 2016-11-19 01:03:51 -08:00
RELEASES.txt brought releases up to date 2016-11-17 10:57:44 -05:00
ROADMAP.rst
setup.py Add ansible-connection to scripts in setup.py 2016-12-05 11:23:04 -05:00
shippable.yml Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
tox.ini
VERSION

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 decide to go with the development branch, be sure to run git submodule update --init --recursive after doing a checkout.

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.
  • As of 1.8, 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.