From 49aa7ee523cf96ff1eb7b17b3add2f9b6e974d1e Mon Sep 17 00:00:00 2001 From: renning bruns Date: Thu, 11 Sep 2014 14:41:51 -0700 Subject: [PATCH] Update playbooks_variables.rst very small and minor addition, but I couldn't find anywhere that answered this (now obvious) question I had of whether or not facts could also be yaml files. --- docsite/rst/playbooks_variables.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index e20e1d6dbe..c5eeff0135 100644 --- a/docsite/rst/playbooks_variables.rst +++ b/docsite/rst/playbooks_variables.rst @@ -667,7 +667,7 @@ For instance, what if you want users to be able to control some aspect about how .. note:: Perhaps "local facts" is a bit of a misnomer, it means "locally supplied user values" as opposed to "centrally supplied user values", or what facts are -- "locally dynamically determined values". If a remotely managed system has an "/etc/ansible/facts.d" directory, any files in this directory -ending in ".fact", can be JSON, INI, or executable files returning JSON, and these can supply local facts in Ansible. +ending in ".fact", can be YAML, JSON, INI, or executable files returning JSON, and these can supply local facts in Ansible. For instance assume a /etc/ansible/facts.d/preferences.fact::