80e7e1a17c
* Due to the takeover of freenode we're moving to a different irc network. * Our channels updated to point at the same channel name on libera.chat * Some links went to webchat.freenode.net. At this time, libera.chat doesn't point you to an official webchat client so I changed these to https://libera.chat. (kiwi irc does work with libera.chat so that could be another option). * In general, I used the name irc.libera.net for link names and https://libera.chat for link targets. This is because the irc service is hosted on irc.libera.chat but the project web server is hosted on libera.chat. (This appears to also be true for freenode but we were using http://irc.freenode.net which doesn't seem to work. Oops). * Removed http://irc.freenode.net from the linkcheck exceptions. linkcheck was actually correct to flag that as invalid (should have been http://frenode.net instead). * Looks like hte important people in #yaml are now in libera.chat * Link to where contributors should get help Add a link target and then link to where contributors should get support for developing groups of modules. * Update docs/docsite/rst/dev_guide/developing_modules_in_groups.rst Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: John R Barker <john@johnrbarker.com> Co-authored-by: Felix Fontein <felix@fontein.de>
70 lines
3.7 KiB
ReStructuredText
70 lines
3.7 KiB
ReStructuredText
.. _modules_support:
|
|
|
|
****************************
|
|
Module Maintenance & Support
|
|
****************************
|
|
|
|
If you are using a module and you discover a bug, you may want to know where to report that bug, who is responsible for fixing it, and how you can track changes to the module. If you are a Red Hat subscriber, you may want to know whether you can get support for the issue you are facing.
|
|
|
|
Starting in Ansible 2.10, most modules live in collections. The distribution method for each collection reflects the maintenance and support for the modules in that collection.
|
|
|
|
.. contents::
|
|
:local:
|
|
|
|
Maintenance
|
|
===========
|
|
|
|
.. table::
|
|
:class: documentation-table
|
|
|
|
============================= ========================================== ==========================
|
|
Collection Code location Maintained by
|
|
============================= ========================================== ==========================
|
|
ansible.builtin `ansible/ansible repo`_ on GitHub core team
|
|
|
|
distributed on Galaxy various; follow ``repo`` link community or partners
|
|
|
|
distributed on Automation Hub various; follow ``repo`` link content team or partners
|
|
============================= ========================================== ==========================
|
|
|
|
.. _ansible/ansible repo: https://github.com/ansible/ansible/tree/devel/lib/ansible/modules
|
|
|
|
Issue Reporting
|
|
===============
|
|
|
|
If you find a bug that affects a plugin in the main Ansible repo, also known as ``ansible-core``:
|
|
|
|
#. Confirm that you are running the latest stable version of Ansible or the devel branch.
|
|
#. Look at the `issue tracker in the Ansible repo <https://github.com/ansible/ansible/issues>`_ to see if an issue has already been filed.
|
|
#. Create an issue if one does not already exist. Include as much detail as you can about the behavior you discovered.
|
|
|
|
If you find a bug that affects a plugin in a Galaxy collection:
|
|
|
|
#. Find the collection on Galaxy.
|
|
#. Find the issue tracker for the collection.
|
|
#. Look there to see if an issue has already been filed.
|
|
#. Create an issue if one does not already exist. Include as much detail as you can about the behavior you discovered.
|
|
|
|
Some partner collections may be hosted in private repositories.
|
|
|
|
If you are not sure whether the behavior you see is a bug, if you have questions, if you want to discuss development-oriented topics, or if you just want to get in touch, use one of our Google groups or IRC channels to :ref:`communicate with Ansiblers <communication>`.
|
|
|
|
If you find a bug that affects a module in an Automation Hub collection:
|
|
|
|
#. If the collection offers an Issue Tracker link on Automation Hub, click there and open an issue on the collection repository. If it does not, follow the standard process for reporting issues on the `Red Hat Customer Portal <https://access.redhat.com/>`_. You must have a subscription to the Red Hat Ansible Automation Platform to create an issue on the portal.
|
|
|
|
Support
|
|
=======
|
|
|
|
All plugins that remain in ``ansible-core`` and all collections hosted in Automation Hub are supported by Red Hat. No other plugins or collections are supported by Red Hat. If you have a subscription to the Red Hat Ansible Automation Platform, you can find more information and resources on the `Red Hat Customer Portal. <https://access.redhat.com/>`_
|
|
|
|
.. seealso::
|
|
|
|
:ref:`intro_adhoc`
|
|
Examples of using modules in /usr/bin/ansible
|
|
:ref:`working_with_playbooks`
|
|
Examples of using modules with /usr/bin/ansible-playbook
|
|
`Mailing List <https://groups.google.com/group/ansible-project>`_
|
|
Questions? Help? Ideas? Stop by the list on Google Groups
|
|
`irc.libera.chat <https://libera.chat/>`_
|
|
#ansible IRC chat channel
|