From 2374abbeda465c0aded55fabc18085a1530c9377 Mon Sep 17 00:00:00 2001 From: Brian Coca Date: Tue, 12 Jan 2016 14:05:33 -0500 Subject: [PATCH] api not thread safe also removed runner ref in general description as it is now a 1.x only thing. --- docsite/rst/developing_api.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docsite/rst/developing_api.rst b/docsite/rst/developing_api.rst index 99dea5d4afa..3fc529758f7 100644 --- a/docsite/rst/developing_api.rst +++ b/docsite/rst/developing_api.rst @@ -6,7 +6,7 @@ Python API There are several interesting ways to use Ansible from an API perspective. You can use the Ansible python API to control nodes, you can extend Ansible to respond to various python events, you can write various plugins, and you can plug in inventory data from external data sources. This document -covers the Runner and Playbook API at a basic level. +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` @@ -17,8 +17,10 @@ This chapter discusses the Python API. .. _python_api: -The Python API is very powerful, and is how the ansible CLI and ansible-playbook -are implemented. In version 2.0 the core ansible got rewritten and the API was mostly rewritten. +The Python API is very powerful, and is how the all the ansible CLI tools are implemented. +In version 2.0 the core ansible got rewritten and the API was mostly rewritten. + +:.. note:: Ansible relies on forking processes, as such teh API is not thread safe. .. _python_api_20: