6 Commits (9edf3a749ac137c8b51b8c7a2ba6c63991f162d5)

Author	SHA1	Message	Date
James Cammarata	365bfd732e	Don't use listify_ function, when all we want to do is template variables ... This was causing a bug in the env module, due to the fact that we now pass variables for the module through the templating engine combined with the fact that we split-up the hostvars and setup variables. As a result, if a variable in the env lookup had the same name as the variable in Ansible, it would try and template itself over and over again until the recursion limit would be hit, at which time an empty string was returned. Fixes #7396	2014-05-20 13:39:23 -05:00
Kahlil (Kal) Hodgson	9f90f0e856	fix arguments to isinstance() in env lookup	2013-04-28 14:58:26 +10:00
C. Morgan Hamill	663d37b537	Fix errors in lookup plugins. ... Lookup plugins 'sequence' and 'template' now import 'ansible.utils' appropriately in order to use the 'listify_lookup_plugin_terms' function. Also, 'dnstxt' and 'env' now check to see if 'terms' is a string; without this calls like '{{ lookup('env', 'HOME') }}' fail.	2013-04-17 11:31:38 -04:00
Michael DeHaan	86d47bce5f	Make more lookup plugins tolerant of new variable system, with a little better 'do what I mean' logic to resolving ... what happens if you get a string back as a template result.	2013-04-16 19:07:19 -04:00
Daniel Hokka Zakrisson	b73016b881	Make all lookup plugins work with lists ... Lookup plugins should accept a string or a list, and always return a list, even if it is just one item.	2012-12-15 21:47:16 +01:00
Jan-Piet Mens	6efc98e8a3	Add environment $LOOKUP plugin ... remove support for multiple vars	2012-11-10 08:26:09 +01:00