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.
Collection | Code location | Maintained by |
---|---|---|
ansible.builtin | ansible/ansible repo on GitHub | core team |
distributed on Galaxy | various; follow | community or partners |
distributed on Automation Hub | various; follow | content team or partners |
If you find a bug that affects a plugin in the main Ansible repo, also known as ansible-base
:
If you find a bug that affects a plugin in a Galaxy collection:
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 communicate with Ansiblers.
If you find a bug that affects a module in an Automation Hub collection:
All plugins that remain in ansible-base
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.
See also
Examples of using modules in /usr/bin/ansible
Examples of using modules with /usr/bin/ansible-playbook
Questions? Help? Ideas? Stop by the list on Google Groups
#ansible IRC chat channel
© 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.11/user_guide/modules_support.html