From 0f2f022bb0760b079bb3cc832b29e986e1bb970b Mon Sep 17 00:00:00 2001 From: Brian Coca Date: Wed, 12 Nov 2014 17:55:58 -0500 Subject: [PATCH] removed YAML as documented local facts format as it is not supported and would require extra modules on target. --- docsite/rst/playbooks_variables.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index f9e3dda4e2..738148106b 100644 --- a/docsite/rst/playbooks_variables.rst +++ b/docsite/rst/playbooks_variables.rst @@ -671,7 +671,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 YAML, JSON, INI, or executable files returning JSON, and these can supply local facts in Ansible. +ending in ".fact", can be 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:: @@ -689,7 +689,7 @@ And you will see the following fact added:: "ansible_local": { "preferences": { "general": { - "asdf" : "1", + "asdf" : "1", "bar" : "2" } } @@ -707,7 +707,7 @@ can allow that fact to be used during that particular play. Otherwise, it will Here is an example of what that might look like:: - hosts: webservers - tasks: + tasks: - name: create directory for ansible custom facts file: state=directory recurse=yes path=/etc/ansible/facts.d - name: install custom impi fact