1Metadata-Version: 1.2 2Name: ansible-core 3Version: 2.11.6 4Summary: Radically simple IT automation 5Home-page: https://ansible.com/ 6Author: Ansible, Inc. 7Author-email: info@ansible.com 8License: GPLv3+ 9Project-URL: Bug Tracker, https://github.com/ansible/ansible/issues 10Project-URL: CI: Azure Pipelines, https://dev.azure.com/ansible/ansible/ 11Project-URL: Code of Conduct, https://docs.ansible.com/ansible/latest/community/code_of_conduct.html 12Project-URL: Documentation, https://docs.ansible.com/ansible/ 13Project-URL: Mailing lists, https://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information 14Project-URL: Source Code, https://github.com/ansible/ansible 15Description: |PyPI version| |Docs badge| |Chat badge| |Build Status| |Code Of Conduct| |Mailing Lists| |License| |CII Best Practices| 16 17 ******* 18 Ansible 19 ******* 20 21 Ansible is a radically simple IT automation system. It handles 22 configuration management, application deployment, cloud provisioning, 23 ad-hoc task execution, network automation, and multi-node orchestration. Ansible makes complex 24 changes like zero-downtime rolling updates with load balancers easy. More information on `the Ansible website <https://ansible.com/>`_. 25 26 Design Principles 27 ================= 28 29 * Have a dead-simple setup process with a minimal learning curve. 30 * Manage machines very quickly and in parallel. 31 * Avoid custom-agents and additional open ports, be agentless by 32 leveraging the existing SSH daemon. 33 * Describe infrastructure in a language that is both machine and human 34 friendly. 35 * Focus on security and easy auditability/review/rewriting of content. 36 * Manage new remote machines instantly, without bootstrapping any 37 software. 38 * Allow module development in any dynamic language, not just Python. 39 * Be usable as non-root. 40 * Be the easiest IT automation system to use, ever. 41 42 Use Ansible 43 =========== 44 45 You can install a released version of Ansible with ``pip`` or a package manager. See our 46 `installation guide <https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html>`_ for details on installing Ansible 47 on a variety of platforms. 48 49 Red Hat offers supported builds of `Ansible Engine <https://www.ansible.com/ansible-engine>`_. 50 51 Power users and developers can run the ``devel`` branch, which has the latest 52 features and fixes, directly. Although it is reasonably stable, you are more likely to encounter 53 breaking changes when running the ``devel`` branch. We recommend getting involved 54 in the Ansible community if you want to run the ``devel`` branch. 55 56 Get Involved 57 ============ 58 59 * Read `Community 60 Information <https://docs.ansible.com/ansible/latest/community>`_ for all 61 kinds of ways to contribute to and interact with the project, 62 including mailing list information and how to submit bug reports and 63 code to Ansible. 64 * Join a `Working Group 65 <https://github.com/ansible/community/wiki>`_, an organized community devoted to a specific technology domain or platform. 66 * Submit a proposed code update through a pull request to the ``devel`` branch. 67 * Talk to us before making larger changes 68 to avoid duplicate efforts. This not only helps everyone 69 know what is going on, but it also helps save time and effort if we decide 70 some changes are needed. 71 * For a list of email lists, IRC channels and Working Groups, see the 72 `Communication page <https://docs.ansible.com/ansible/latest/community/communication.html>`_ 73 74 Coding Guidelines 75 ================= 76 77 We document our Coding Guidelines in the `Developer Guide <https://docs.ansible.com/ansible/devel/dev_guide/>`_. We particularly suggest you review: 78 79 * `Contributing your module to Ansible <https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_checklist.html>`_ 80 * `Conventions, tips, and pitfalls <https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_best_practices.html>`_ 81 82 Branch Info 83 =========== 84 85 * The ``devel`` branch corresponds to the release actively under development. 86 * The ``stable-2.X`` branches correspond to stable releases. 87 * Create a branch based on ``devel`` and set up a `dev environment <https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general.html#common-environment-setup>`_ if you want to open a PR. 88 * See the `Ansible release and maintenance <https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html>`_ page for information about active branches. 89 90 Roadmap 91 ======= 92 93 Based on team and community feedback, an initial roadmap will be published for a major or minor version (ex: 2.7, 2.8). 94 The `Ansible Roadmap page <https://docs.ansible.com/ansible/devel/roadmap/>`_ details what is planned and how to influence the roadmap. 95 96 Authors 97 ======= 98 99 Ansible was created by `Michael DeHaan <https://github.com/mpdehaan>`_ 100 and has contributions from over 5000 users (and growing). Thanks everyone! 101 102 `Ansible <https://www.ansible.com>`_ is sponsored by `Red Hat, Inc. 103 <https://www.redhat.com>`_ 104 105 License 106 ======= 107 108 GNU General Public License v3.0 or later 109 110 See `COPYING <COPYING>`_ to see the full text. 111 112 .. |PyPI version| image:: https://img.shields.io/pypi/v/ansible-core.svg 113 :target: https://pypi.org/project/ansible-core 114 .. |Docs badge| image:: https://img.shields.io/badge/docs-latest-brightgreen.svg 115 :target: https://docs.ansible.com/ansible/latest/ 116 .. |Build Status| image:: https://dev.azure.com/ansible/ansible/_apis/build/status/CI?branchName=devel 117 :target: https://dev.azure.com/ansible/ansible/_build/latest?definitionId=20&branchName=devel 118 .. |Chat badge| image:: https://img.shields.io/badge/chat-IRC-brightgreen.svg 119 :target: https://docs.ansible.com/ansible/latest/community/communication.html 120 .. |Code Of Conduct| image:: https://img.shields.io/badge/code%20of%20conduct-Ansible-silver.svg 121 :target: https://docs.ansible.com/ansible/latest/community/code_of_conduct.html 122 :alt: Ansible Code of Conduct 123 .. |Mailing Lists| image:: https://img.shields.io/badge/mailing%20lists-Ansible-orange.svg 124 :target: https://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information 125 :alt: Ansible mailing lists 126 .. |License| image:: https://img.shields.io/badge/license-GPL%20v3.0-brightgreen.svg 127 :target: COPYING 128 :alt: Repository License 129 .. |CII Best Practices| image:: https://bestpractices.coreinfrastructure.org/projects/2372/badge 130 :target: https://bestpractices.coreinfrastructure.org/projects/2372 131 :alt: Ansible CII Best Practices certification 132 133Platform: UNKNOWN 134Classifier: Development Status :: 5 - Production/Stable 135Classifier: Environment :: Console 136Classifier: Intended Audience :: Developers 137Classifier: Intended Audience :: Information Technology 138Classifier: Intended Audience :: System Administrators 139Classifier: License :: OSI Approved :: GNU General Public License v3 or later (GPLv3+) 140Classifier: Natural Language :: English 141Classifier: Operating System :: POSIX 142Classifier: Programming Language :: Python :: 2 143Classifier: Programming Language :: Python :: 2.7 144Classifier: Programming Language :: Python :: 3 145Classifier: Programming Language :: Python :: 3.5 146Classifier: Programming Language :: Python :: 3.6 147Classifier: Programming Language :: Python :: 3.7 148Classifier: Programming Language :: Python :: 3.8 149Classifier: Programming Language :: Python :: 3.9 150Classifier: Topic :: System :: Installation/Setup 151Classifier: Topic :: System :: Systems Administration 152Classifier: Topic :: Utilities 153Requires-Python: >=2.7,!=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*,!=3.4.* 154