ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-10-05 07:54:00 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Fix all RST errors for docs/docsite/rst (#20005)

Browse source 
* developing_modules.rst is now in dev_guide, sync changes and delete the old version
* Cleaner RST & formatted code
* Tidyup roadmaps
* Link to repomerge
* Pull in abadger's fixes From https://github.com/ansible/ansible/compare/docs-code-block-fixes?expand=1
* Clean docsite/rst (apart from ROADMAP
This commit is contained in:
John R Barker 2017-01-07 19:38:52 +00:00 • committed by Toshio Kuratomi
commit 7df31aaca1
38 changed files with 464 additions and 1096 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/docsite/rst/dev_guide/developing_api.rst
View file

@ -16,7 +16,7 @@ write various plugins, and you can plug in inventory data from external data sou
covers the execution and Playbook API at a basic level.
If you are looking to use Ansible programmatically from something other than Python, trigger events asynchronously,
or have access control and logging demands, take a look at :doc:`tower`
or have access control and logging demands, take a look at :doc:`../tower`
as it has a very nice REST API that provides all of these things at a higher level.
Ansible is written in its own API so you have a considerable amount of power across the board.
@ -125,7 +125,7 @@ It's pretty simple::
The run method returns results per host, grouped by whether they
could be contacted or not. Return types are module specific, as
expressed in the :doc:`modules` documentation.::
expressed in the :doc:`../modules` documentation.::
{
"dark" : {