From 864928365ef000c187871e6874b520f0bd2bc97c Mon Sep 17 00:00:00 2001 From: Old Schepperhand Date: Wed, 18 Sep 2019 22:04:44 +0200 Subject: [PATCH] Improve dconf documentation to include conversion problems (#62316) --- lib/ansible/modules/system/dconf.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/lib/ansible/modules/system/dconf.py b/lib/ansible/modules/system/dconf.py index 8183b07648d..fce014b254a 100644 --- a/lib/ansible/modules/system/dconf.py +++ b/lib/ansible/modules/system/dconf.py @@ -39,6 +39,10 @@ notes: wanted to provide a string value, the correct syntax would be C(value="'myvalue'") - with single quotes as part of the Ansible parameter value. + - When using loops in combination with a value like + :code:`"[('xkb', 'us'), ('xkb', 'se')]"`, you need to be aware of possible + type conversions. Applying a filter :code:`"{{ item.value | string }}"` + to the parameter variable can avoid potential conversion problems. - The easiest way to figure out exact syntax/value you need to provide for a key is by making the configuration change in application affected by the key, and then having a look at value set via commands C(dconf dump