ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Specified when PIPE_ONCE was added.

Browse source 
Also, now shows when "Getting values from files" was added, a sphinx
directive was missing a colon.
This commit is contained in:
Lorin Hochstein 2013-02-17 12:55:47 -05:00
parent ec16b854a5
commit c6778e796c
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docsite/rst/playbooks2.rst
View file

@ -567,7 +567,7 @@ Negative numbers are not supported. This works as follows::
Getting values from files Getting values from files
````````````````````````` `````````````````````````
.. versionadded: 0.8 .. versionadded:: 0.8
Sometimes you'll want to include the content of a file directly into a playbook. You can do so using a macro. Sometimes you'll want to include the content of a file directly into a playbook. You can do so using a macro.
This syntax will remain in future versions, though we will also will provide ways to do this via lookup plugins (see "More Loops") as well. What follows This syntax will remain in future versions, though we will also will provide ways to do this via lookup plugins (see "More Loops") as well. What follows
@ -587,6 +587,8 @@ Because Ansible uses lazy evaluation, a "$PIPE" macro will be executed each time
example, it will be executed separately for each host, and if it is used in a variable definition, example, it will be executed separately for each host, and if it is used in a variable definition,
it will be executed each time the variable is evaluated. it will be executed each time the variable is evaluated.
.. versionadded:: 1.1
The "$PIPE_ONCE" macro is an alternative that uses a caching strategy: it is executed only once, and The "$PIPE_ONCE" macro is an alternative that uses a caching strategy: it is executed only once, and
subsequent accesses use the cached value. One use case is for computing a timestamp that is intended subsequent accesses use the cached value. One use case is for computing a timestamp that is intended
to be the same across all tasks and hosts that use it:: to be the same across all tasks and hosts that use it::