Adrian Likins 9cc63326b1 Misc docsite fixes (#30290 )

* Fix refs for local_facts and various cli :option:
* Fix dev_guide/testing_pep8 refs
* remove ref to non-existing 'developing_test_pr'
* Fix ref to ansible-vault encrypt_string
* Removed hard-to-localize colloquialism.
* Rename '_ansible-pull' in playbooks_intro.

It was conflicting with rst/ansible-pull.rst. Nothing
seems to reference it.

* Add explicit targets for and update refs

Replace some ':doc:' use with ':ref:'.

Replace some :ref: to section names with explicit targets
(:doc:`Dynamic vs. Static` -> :ref:`dynamic_vs_static` etc)

* The 'YAML+Jinja' syntax lex fails here, so just use yaml

Since the yaml+jinja highlight fails, code wasnt highlighted
at all, but 'yaml' works more or less.

* just use no lexer for the < python2.6 examples

py3 will fail highlighting them, and 'python2' throws
a lexer warning, and nothing actually highlights it, so
just disable.

2017-09-14 11:17:56 -04:00

3.1 KiB

Raw Blame History

Module Maintenance & Support

maxdepth: 1

To help identify maintainers and understand how the included modules are officially supported, each module now has associated metadata that provides additional clarity for maintenance and support.

Core

Core modules are maintained by the Ansible Engineering Team<core_maintained>. These modules are integral to the basic foundations of the Ansible distribution.

Network

Network modules are maintained by the Ansible Network Team<network_maintained>. Please note there are additional networking modules<list_of_network_modules> that are categorized as Certified or Community not maintained by Ansible.

Certified

Certified modules are part of a future planned program currently in development.

Community

Community modules are submitted and maintained by the Ansible community<community_maintained>. These modules are not maintained by Ansible, and are included as a convenience.

Issue Reporting

If you believe you have found a bug in a module and are already running the latest stable or development version of Ansible, first look at the issue tracker in the Ansible repo to see if an issue has already been filed. If not, please file one.

Should you have a question rather than a bug report, inquiries are welcome on the ansible-project Google group or on Ansible’s “#ansible” channel, located on irc.freenode.net.

For development-oriented topics, use the ansible-devel Google group or Ansible’s #ansible and #ansible-devel channels, located on irc.freenode.net. You should also read Community Information & Contributing <community>, Testing Ansible <dev_guide/testing>, and Developing Modules <dev_guide/developing_modules>.

The modules are hosted on GitHub in a subdirectory of the Ansible repo.

NOTE: If you have a Red Hat Ansible Engine product subscription, please follow the standard issue reporting process via the Red Hat Customer Portal.

Support

For more information on how included Ansible modules are supported by Red Hat, please refer to the following knowledgebase article as well as other resources on the Red Hat Customer Portal.

intro_adhoc: Examples of using modules in /usr/bin/ansible
playbooks: Examples of using modules with /usr/bin/ansible-playbook
dev_guide/developing_modules: How to write your own modules
dev_guide/developing_api: Examples of using modules with the Python API
Mailing List: Questions? Help? Ideas? Stop by the list on Google Groups
irc.freenode.net: #ansible IRC chat channel

3.1 KiB Raw Blame History Unescape Escape