From fafcb3452f9636843718b0fcddd374a2866ed9ad Mon Sep 17 00:00:00 2001 From: Toshio Kuratomi Date: Thu, 8 Mar 2018 16:02:43 -0800 Subject: [PATCH] Porting guide (#37226) * Add the lookup plugin strictness to the porting guide * Edited for clarity. * Wordsmithing. --- docs/docsite/rst/porting_guides/porting_guide_2.5.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/docsite/rst/porting_guides/porting_guide_2.5.rst b/docs/docsite/rst/porting_guides/porting_guide_2.5.rst index fc686be7b3e..d6b68effc26 100644 --- a/docs/docsite/rst/porting_guides/porting_guide_2.5.rst +++ b/docs/docsite/rst/porting_guides/porting_guide_2.5.rst @@ -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, 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 ======================