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
Toshio Kuratomi 1efe782b46 Refactor parsing of CLI args so that we can modify them in the base class
Implement tag and skip_tag handling in the CLI() class.  Change tag and
skip_tag command line options to be accepted multiple times on the CLI
and add them together rather than overwrite.

* Make it configurable whether to merge or overwrite multiple --tags arguments
* Make the base CLI class an abstractbaseclass so we can implement
  functionality in parse() but still make subclasses implement it.
* Deprecate the overwrite feature of --tags with a message that the
  default will change in 2.4 and go away in 2.5.

* Add documentation for merge_multiple_cli_flags
* Fix galaxy search so its tags argument does not conflict with generic tags
* Unit tests and more integration tests for tags
2016-10-06 10:46:58 -04:00
.github Try to avoid module-related tickets in the core Ansible project (#17047) 2016-08-11 10:14:27 -04:00
bin Fixes to the controller text model (#17527) 2016-09-12 12:57:41 -07:00
contrib vmware_inventory: Make the ceritifate check default, and create a config option (#17830) 2016-09-30 09:06:02 -04:00
docs/man added new ksu method to man page 2016-09-13 14:40:41 -04:00
docs-api updated devel to 2.3 (#17884) 2016-10-03 15:08:19 -04:00
docsite Refactor parsing of CLI args so that we can modify them in the base class 2016-10-06 10:46:58 -04:00
examples Refactor parsing of CLI args so that we can modify them in the base class 2016-10-06 10:46:58 -04:00
hacking added script to unify repos 2016-10-03 22:55:38 -04:00
lib/ansible Refactor parsing of CLI args so that we can modify them in the base class 2016-10-06 10:46:58 -04:00
packaging Updating CHANGELOG and release versions for 2.1.2 2016-10-03 09:31:12 -05:00
test Refactor parsing of CLI args so that we can modify them in the base class 2016-10-06 10:46:58 -04:00
ticket_stubs Add proposals template (#16654) 2016-07-08 17:04:03 -04:00
.coveragerc Add tox and travis-ci support 2015-03-13 08:20:24 -04:00
.gitattributes updated changelog with 1.8.2-4 content, added .gitattributes 2015-02-23 22:20:33 +00:00
.gitignore Change default theme to 'alabaster' 2016-06-30 16:54:21 -04:00
.gitmodules remove old dead code 2015-08-27 12:27:38 -04:00
.mailmap Add a .mailmap for 'shortlog' (#15588) 2016-04-25 17:18:14 -04:00
.yamllint Fix YAML source and check it on Shippable (#15678) 2016-06-04 10:58:17 -07:00
ansible-core-sitemap.xml Add debug strategy plugin (#15125) 2016-04-08 14:39:08 -04:00
CHANGELOG.md asa_template wasn't ever officially released 2016-10-04 14:07:01 +01:00
CODING_GUIDELINES.md Migrate basestring to a python3 compatible type (#17199) 2016-08-23 13:13:44 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md with more recent developments 2016-03-23 15:32:29 +01:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Add '--cover-erase' to 'make tests' cli (#17708) 2016-09-22 13:35:18 -07:00
MANIFEST.in added galaxy data 2016-01-12 16:22:01 +01:00
README.md Remove download stats badge (#16358) 2016-06-20 10:14:37 -04:00
RELEASES.txt updated devel to 2.3 (#17884) 2016-10-03 15:08:19 -04:00
ROADMAP.rst updated devel to 2.3 (#17884) 2016-10-03 15:08:19 -04:00
setup.py Fix ziploader for the cornercase of ansible invoking ansible. 2016-04-29 08:47:49 -07:00
shippable.yml Add PRIVILEGED to freebsd because testing of mount keys off of that. (#17803) 2016-09-28 23:33:28 -07:00
tox.ini We've decided that python-3.5 is the minimum python version (#17270) 2016-08-29 09:12:37 -07:00
VERSION Bumping devel version to 2.3.0 2016-10-03 11:46:31 -05:00

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 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 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