mirror of https://github.com/ansible/ansible.git
Mirror of https://github.com/ansible/ansible.git
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.
15d76d97a9
In "status: present" playbook execution for a VDO volume that is absent, all of the parameters that are given in the playbook are issued to the "vdo create" command, therefore any parameters that become "unrecognized" will result in the "vdo" command returning an error with the message "unrecognized arguments", which can then be relayed back to the user. This is a gracefully handled failure case. Examples of "unrecognized" parameters are new features that are not yet in the current version of VDO, or features that were removed since the current version of VDO. In "status: present" playbook execution for a VDO volume that is already present, the same behavior as the "creation" stage of the module should occur, but doesn't occur, since the key strings for the "vdo status" output of the parameter do not exist. This results in a KeyError on the parameter that no longer exists. Therefore, use "if statfield in processedvdos[desiredvdo]:" to filter the modifiable parameters with the ones that are supported in this VDO version, then use "if statfield not in processedvdos[desiredvdo]:" to evade the KeyError, and add the "unsupported" parameters. Also, instead of using the "currentvdoparams" dictionary, which filters only the parameters reported by the "vdo status" output, use the "modtrans" dictionary, which contains all of the possible parameters. Therefore, if the playbook specifies an "unsupported" parameter, let it be passed on to the "vdo" command, to display an actionable error message. This fixes https://github.com/ansible/ansible/issues/54556 Signed-off-by: Bryan Gurney <bgurney@redhat.com> |
5 years ago | |
|---|---|---|
| .github | 5 years ago | |
| bin | 5 years ago | |
| changelogs | 5 years ago | |
| contrib | 5 years ago | |
| docs | 5 years ago | |
| examples | 5 years ago | |
| hacking | 5 years ago | |
| lib/ansible | 5 years ago | |
| licenses | 6 years ago | |
| packaging | 5 years ago | |
| test | 5 years ago | |
| .cherry_picker.toml | 6 years ago | |
| .coveragerc | 6 years ago | |
| .gitattributes | 7 years ago | |
| .gitignore | 6 years ago | |
| .mailmap | 7 years ago | |
| CODING_GUIDELINES.md | 6 years ago | |
| COPYING | 13 years ago | |
| MANIFEST.in | 6 years ago | |
| MODULE_GUIDELINES.md | 6 years ago | |
| Makefile | 6 years ago | |
| README.rst | 6 years ago | |
| requirements.txt | 6 years ago | |
| setup.py | 5 years ago | |
| shippable.yml | 5 years ago | |
| tox.ini | 6 years ago | |
README.rst
|PyPI version| |Docs badge| |Chat badge| |Build Status| |Code Of Conduct| |Mailing Lists| |License| ******* Ansible ******* Ansible is a radically simple IT automation system. It handles configuration management, application deployment, cloud provisioning, ad-hoc task execution, network automation, and multi-node orchestration. Ansible makes complex changes like zero-downtime rolling updates with load balancers easy. More information on `the Ansible website <https://ansible.com/>`_. 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. Use Ansible =========== You can install a released version of Ansible via ``pip``, a package manager, or our `release repository <https://releases.ansible.com/ansible/>`_. See our `installation guide <https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html>`_ for details on installing Ansible on a variety of platforms. Red Hat offers supported builds of `Ansible Engine <https://www.ansible.com/ansible-engine>`_. Power users and developers can run the ``devel`` branch, which has the latest features and fixes, directly. Although it is reasonably stable, you are more likely to encounter breaking changes when running the ``devel`` branch. We recommend getting involved in the Ansible community if you want to run the ``devel`` branch. Get Involved ============ * Read `Community Information <https://docs.ansible.com/ansible/latest/community>`_ 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. * Join a `Working Group <https://github.com/ansible/community/wiki>`_, an organized community devoted to a specific technology domain or platform. * Submit a proposed code update through a pull request to the ``devel`` branch. * Talk to us before making larger changes to avoid duplicate efforts. This not only helps everyone know what is going on, it also helps save time and effort if we decide some changes are needed. * For a list of email lists, IRC channels and Working Groups, see the `Communication page <https://docs.ansible.com/ansible/latest/community/communication.html>`_ Branch Info =========== * The ``devel`` branch corresponds to the release actively under development. * The ``stable-2.X`` branches correspond to stable releases. * 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. * See the `Ansible release and maintenance <https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html>`_ page for information about active branches. Roadmap ======= Based on team and community feedback, an initial roadmap will be published for a major or minor version (ex: 2.7, 2.8). The `Ansible Roadmap page <https://docs.ansible.com/ansible/devel/roadmap/>`_ details what is planned and how to influence the roadmap. Authors ======= Ansible was created by `Michael DeHaan <https://github.com/mpdehaan>`_ and has contributions from over 4000 users (and growing). Thanks everyone! `Ansible <https://www.ansible.com>`_ is sponsored by `Red Hat, Inc. <https://www.redhat.com>`_ License ======= GNU General Public License v3.0 See `COPYING <COPYING>`_ to see the full text. .. |PyPI version| image:: https://img.shields.io/pypi/v/ansible.svg :target: https://pypi.org/project/ansible .. |Docs badge| image:: https://img.shields.io/badge/docs-latest-brightgreen.svg :target: https://docs.ansible.com/ansible/latest/ .. |Build Status| image:: https://api.shippable.com/projects/573f79d02a8192902e20e34b/badge?branch=devel :target: https://app.shippable.com/projects/573f79d02a8192902e20e34b .. |Chat badge| image:: https://img.shields.io/badge/chat-IRC-brightgreen.svg :target: https://docs.ansible.com/ansible/latest/community/communication.html .. |Code Of Conduct| image:: https://img.shields.io/badge/code%20of%20conduct-Ansible-silver.svg :target: https://docs.ansible.com/ansible/latest/community/code_of_conduct.html :alt: Ansible Code of Conduct .. |Mailing Lists| image:: https://img.shields.io/badge/mailing%20lists-Ansible-orange.svg :target: https://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information :alt: Ansible mailing lists .. |License| image:: https://img.shields.io/badge/license-GPL%20v3.0-brightgreen.svg :target: COPYING :alt: Repository License