ansible/docs/docsite/rst/dev_guide/developing_modules.rst
Jordan Borean ad5fa60a2b Added initial developing module doc for Windows (#27308)
* Added initial developing module doc for Windows

* Added to dev index, made formatting changes and moved obsolete docs

* changes based on PR feedback

* some typos and extra information

* Minor updates

* minor wording clarifications
* remove references to "remote" Windows hosts
* update template/text to remove legacy `#WANT_JSON`/`#POWERSHELL_COMMON`
* use per-execution envvars for ANSIBLE_KEEP_REMOTE_FILES instead of stateful

* fix up minor sanity check issue
2017-08-01 08:02:56 +10:00

4 KiB

Developing Modules

Topics

Welcome

This section discusses how to develop, debug, review, and test modules.

Ansible modules are reusable, standalone scripts that can be used by the Ansible API, or by the ansible or ansible-playbook programs. They return information to ansible by printing a JSON string to stdout before exiting. They take arguments in one of several ways which we'll go into as we work through this tutorial.

See ../modules for a list of existing modules.

Modules can be written in any language and are found in the path specified by ANSIBLE_LIBRARY or the --module-path command line option or in the library section of the Ansible configuration file.

Should You Develop A Module?

Before diving into the work of creating a new module, you should think about whether you actually should develop a module. Ask the following questions:

  1. Does a similar module already exist?

There are a lot of existing modules available, you should check out the list of existing modules at ../modules

  1. Has someone already worked on a similar Pull Request?

It's possible that someone has already started developing a similar PR. There are a few ways to find open module Pull Requests:

If you find an existing PR that looks like it addresses the issue you are trying to solve, please provide feedback on the PR - this will speed up getting the PR merged.

  1. Should you use or develop an action plugin instead?

Action plugins get run on the master instead of on the target. For modules like file/copy/template, some of the work needs to be done on the master before the module executes on the target. Action plugins execute first on the master and can then execute the normal module on the target if necessary.

For more information about action plugins, read the action plugins documentation here.

  1. Should you use a role instead?

Check out the roles documentation available here.

How To Develop A Module

The following topics will discuss how to develop and work with modules:

developing_modules_general

A general overview of how to develop, debug, and test modules.

developing_modules_general_windows

A general overview of how to develop, debug and test Windows modules.

developing_modules_documenting

How to include in-line documentation in your module.

developing_modules_best_practices

Best practices, recommendations, and things to avoid.

developing_modules_checklist

Checklist for contributing your module to Ansible.

testing

Developing unit and integration tests.

developing_python3

Adding Python 3 support to modules (all new modules must be Python-2.6 and Python-3.5 compatible).

developing_modules_in_groups

A guide for partners wanting to submit multiple modules.

../modules

Learn about available modules

developing_plugins

Learn about developing plugins

developing_api

Learn about the Python API for playbook and task execution

GitHub modules directory

Browse module source code

Mailing List

Development mailing list

irc.freenode.net

#ansible IRC chat channel