6d5f2dccb2
* 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.
(cherry picked from commit 9cc63326b1)
38 lines
1,021 B
ReStructuredText
38 lines
1,021 B
ReStructuredText
*********************
|
|
Developer Information
|
|
*********************
|
|
|
|
Ansible Developer Guide
|
|
=======================
|
|
|
|
Welcome to the Ansible Developer Guide!
|
|
|
|
The purpose of this guide is to document all of the paths available to you for interacting and shaping Ansible with code, ranging from developing modules and plugins to helping to develop the Ansible Core Engine via pull requests.
|
|
|
|
To get started, select one of the following topics.
|
|
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
overview_architecture
|
|
developing_modules
|
|
developing_modules_general
|
|
developing_modules_general_windows
|
|
developing_modules_documenting
|
|
developing_modules_best_practices
|
|
developing_modules_checklist
|
|
developing_modules_in_groups
|
|
developing_program_flow_modules
|
|
developing_module_utilities
|
|
developing_plugins
|
|
developing_inventory
|
|
developing_core
|
|
developing_python3
|
|
developing_api
|
|
developing_rebasing
|
|
testing
|
|
repomerge
|
|
../release_and_maintenance
|
|
../committer_guidelines
|
|
./style_guide/index
|