Developer Guide

[!NOTE] Making Open Source More Inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. We ask that you open an issue or pull request if you come upon a term that we have missed. For more details, see our CTO Chris Wright's message.

Welcome to the Ansible Developer Guide!

Who should use this guide?

If you want to extend Ansible by using a custom module or plugin locally, creating a module or plugin, adding functionality to an existing module, or expanding test coverage, this guide is for you. We've included detailed information for developers on how to test and document modules, as well as the prerequisites for getting your module or plugin accepted into the main Ansible repository.

Find the task that best describes what you want to do:

• I'm looking for a way to address a use case:

  • I want to add a custom plugin or module locally <developing_locally>.
  • I want to figure out if developing a module is the right approach <module_dev_should_you> for my use case.
  • I want to understand what a successful collection creator path looks like <developing_collections_path>.
  • I want to develop a collection <developing_collections>.
  • I want to contribute to an Ansible-maintained collection <contributing_maintained_collections>.
  • I want to contribute to a community-maintained collection <hacking_collections>.
  • I want to migrate a role to a collection <migrating_roles>.

• I've read the info above, and I'm sure I want to develop a module:

  • What do I need to know before I start coding?

  • I want to set up my Python development environment <environment_setup>.

  • I want to get started writing a module <developing_modules_general>.

  • I want to write a specific kind of module:

    • a network module <developing_modules_network>
    • a Windows module <developing_modules_general_windows>.
    • an Amazon module <ansible_collections.amazon.aws.docsite.dev_guide_intro>.
    • an oVirt/RHV module.
    • a VMware module <ansible_collections.community.vmware.docsite.vmware_ansible_devguide>.

  • I want to write a series of related modules <developing_modules_in_groups> that integrate Ansible with a new product (for example, a database, cloud provider, network platform, and so on).

• I want to refine my code:

  • I want to debug my module code <debugging_modules>.
  • I want to add tests <developing_testing>.
  • I want to document my module <module_documenting>.
  • I want to improve documentation by using Ansible markup <ansible_markup>.
  • I want to document my set of modules for a network platform <documenting_modules_network>.
  • I want to follow conventions and tips for clean, usable module code <developing_modules_best_practices>.
  • I want to make sure my code runs on Python 2 and Python 3 <developing_python_3>.

• I want to work on other development projects:

  • I want to write a plugin <developing_plugins>.
  • I want to connect Ansible to a new source of inventory <developing_inventory>.
  • I want to deprecate an outdated module <deprecating_modules>.

• I want to contribute back to the Ansible project:

  • I want to understand how to contribute to Ansible <ansible_community_guide>.
  • I want to contribute my module or plugin <developing_modules_checklist>.
  • I want to understand the DCO agreement <developer_certificate_of_origin> for contributions to the Ansible Core and Ansible Documentation repositories.

If you prefer to read the entire guide, here's a list of the pages in order.