ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Update playbooks_variables.rst

Browse source 
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.
This commit is contained in:
renning bruns 2014-09-11 14:41:51 -07:00
parent fb13e2bf2e
commit 49aa7ee523
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docsite/rst/playbooks_variables.rst
View file

@ -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". .. 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 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:: For instance assume a /etc/ansible/facts.d/preferences.fact::