mirror of https://github.com/ansible/ansible.git
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
54 lines
2.3 KiB
ReStructuredText
54 lines
2.3 KiB
ReStructuredText
Lookups
|
|
-------
|
|
|
|
Lookup plugins allow access to outside data sources. Like all templating, these plugins are evaluated on the Ansible control machine, and can include reading the filesystem as well as contacting external datastores and services. This data is then made available using the standard templating system in Ansible.
|
|
|
|
.. note::
|
|
- Lookups occur on the local computer, not on the remote computer.
|
|
- They are executed with in the directory containing the role or play, as opposed to local tasks which are executed with the directory of the executed script.
|
|
- Since Ansible version 1.9, you can pass wantlist=True to lookups to use in jinja2 template "for" loops.
|
|
- Lookups are an advanced feature. You should have a good working knowledge of Ansible plays before incorporating them.
|
|
|
|
.. warning:: Some lookups pass arguments to a shell. When using variables from a remote/untrusted source, use the `|quote` filter to ensure safe usage.
|
|
|
|
.. contents:: Topics
|
|
|
|
.. _lookups_and_loops:
|
|
|
|
Lookups and loops
|
|
`````````````````
|
|
|
|
Various *lookup plugins* allow additional ways to iterate over data.
|
|
In :doc:`Loops <playbooks_loops>` you will learn how to use them to walk over collections of numerous types.
|
|
However, they can also be used to pull in data from remote sources, such as shell commands or even key value stores.
|
|
Before Ansible 2.5, lookups were mostly used indirectly in ``with_<lookup`` constructes for looping, begining in 2.5
|
|
we use them more explicitly as part of Jinja2 expressions fed into the ``loop`` keyword.
|
|
|
|
|
|
.. _lookups_and_variables:
|
|
|
|
Lookups and variables
|
|
`````````````````````
|
|
|
|
One way of using lookups is to populate variables. These macros are evaluated each time they are used in a task (or template)::
|
|
|
|
vars:
|
|
motd_value: "{{ lookup('file', '/etc/motd') }}"
|
|
tasks:
|
|
- debug: msg="motd value is {{ motd_value }}"
|
|
|
|
.. seealso::
|
|
|
|
:doc:`playbooks`
|
|
An introduction to playbooks
|
|
:doc:`playbooks_conditionals`
|
|
Conditional statements in playbooks
|
|
:doc:`playbooks_variables`
|
|
All about variables
|
|
:doc:`playbooks_loops`
|
|
Looping in playbooks
|
|
`User Mailing List <http://groups.google.com/group/ansible-devel>`_
|
|
Have a question? Stop by the google group!
|
|
`irc.freenode.net <http://irc.freenode.net>`_
|
|
#ansible IRC chat channel
|