cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Porting guide (#37226)

Browse source 
* Add the lookup plugin strictness to the porting guide

* Edited for clarity.

* Wordsmithing.
This commit is contained in:
Toshio Kuratomi 2018-03-08 16:02:43 -08:00 committed by GitHub
parent 708869edd6
commit fafcb3452f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/docsite/rst/porting_guides/porting_guide_2.5.rst
View file

@ -188,6 +188,11 @@ For a full list, check the shell plugin you are using, the default shell plugin
Those that had to work around the global configuration limitations can now migrate to a per host/group settings, Those that had to work around the global configuration limitations can now migrate to a per host/group settings,
but also note that the new defaults might conflict with existing usage if the assumptions don't correlate to your environment. but also note that the new defaults might conflict with existing usage if the assumptions don't correlate to your environment.
Filter
------
The lookup plugin API now throws an error if a non-iterable value is returned from a plugin. Previously, numbers or
other non-iterable types returned by a plugin were accepted without error or warning. This change was made because plugins should always return a list. Please note that plugins that return strings and other non-list iterable values will not throw an error, but may cause unpredictable behavior. If you have a custom lookup plugin that does not return a list, you should modify it to wrap the return values in a list.
Porting custom scripts Porting custom scripts
====================== ======================