From deb5f027f03a5c64ed2675a7aeac559dabccd253 Mon Sep 17 00:00:00 2001 From: James Cammarata Date: Fri, 23 Aug 2013 11:33:57 -0500 Subject: [PATCH] Fixed up a few other pages that had the same versionadded error --- docsite/latest/rst/api.rst | 6 +++--- docsite/latest/rst/playbooks2.rst | 10 +++++----- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docsite/latest/rst/api.rst b/docsite/latest/rst/api.rst index 78b48fe146d..b07cba206d3 100644 --- a/docsite/latest/rst/api.rst +++ b/docsite/latest/rst/api.rst @@ -122,7 +122,7 @@ simply a list of host/IP addresses, like so:: "5points" : [ "host7.example.com" ] } -.. versionadded: 1.0 +.. versionadded:: 1.0 Before version 1.0, each group could only have a list of hostnames/IP addresses, like the webservers, marietta, and 5points groups above. @@ -139,7 +139,7 @@ if the script does not wish to do this, returning an empty hash/dictionary is th Tuning the External Inventory Script ```````````````````````````````````` -.. versionadded: 1.3 +.. versionadded:: 1.3 The stock inventory script system detailed above works for all versions of Ansible, but calling '--host' for every host can be rather expensive, especially if it involves expensive API calls to @@ -370,7 +370,7 @@ If you want more Jinja2 filters available in a Jinja2 template (filters like to_ Distributing Plugins -------------------- -.. versionadded: 0.8 +.. versionadded:: 0.8 Plugins are loaded from both Python's site_packages (those that ship with ansible) and a configured plugins directory, which defaults to /usr/share/ansible/plugins, in a subfolder for each plugin type:: diff --git a/docsite/latest/rst/playbooks2.rst b/docsite/latest/rst/playbooks2.rst index d4bccfabfc5..5c006c0edfb 100644 --- a/docsite/latest/rst/playbooks2.rst +++ b/docsite/latest/rst/playbooks2.rst @@ -515,7 +515,7 @@ As with the case of 'with_items' above, you can use previously defined variables Lookup Plugins - Accessing Outside Data ``````````````````````````````````````` -.. versionadded: 0.8 +.. versionadded:: 0.8 Various *lookup plugins* allow additional ways to iterate over data. Ansible will have more of these over time. You can write your own, as is covered in the API section. Each typically takes a list and @@ -549,7 +549,7 @@ be used like this:: specify a relative path (e.g., :file:`./foo`), Ansible resolves the path relative to the :file:`roles//files` directory. -.. versionadded: 0.9 +.. versionadded:: 0.9 Many new lookup abilities were added in 0.9. Remember, lookup plugins are run on the *controlling* machine:: @@ -582,7 +582,7 @@ template):: tasks: - debug: msg="motd value is {{ motd_value }}" -.. versionadded: 1.0 +.. versionadded:: 1.0 ``with_sequence`` generates a sequence of items in ascending numerical order. You can specify a start, end, and an optional step value. @@ -614,7 +614,7 @@ Negative numbers are not supported. This works as follows:: - group: name=group{{ item }} state=present with_sequence: count=4 -.. versionadded: 1.1 +.. versionadded:: 1.1 ``with_password`` and associated lookup macro generate a random plaintext password and store it in a file at a given filepath. Support for crypted save modes (as with vars_prompt) is pending. If the @@ -657,7 +657,7 @@ This length can be changed by passing an extra parameter:: Setting the Environment (and Working With Proxies) `````````````````````````````````````````````````` -.. versionadded: 1.1 +.. versionadded:: 1.1 It is quite possible that you may need to get package updates through a proxy, or even get some package updates through a proxy and access other packages not through a proxy. Ansible makes it easy for you