Local facts for Windows have been available since 2.1- you just need to set fact_path to tell it where on the target system to find a directory of .ps1 scripts to execute. It currently expects to find a dictionary/array on the output pipeline from each script that gets grafted onto a new fact named ansible_(factsfilename-sans-extension).
On Tuesday, September 13, 2016 at 3:54:35 AM UTC-7, Mike Fennemore wrote: > > Nevermind, to answer my own question > http://docs.ansible.com/ansible/developing_modules.html#module-provided-facts > . Although this does add the hassle of adding a custom module to playbooks. > It would be nice to have a hook to add a module to run on playbook > execution like the setup module though. > > On Tuesday, September 13, 2016 at 11:14:40 AM UTC+2, Mike Fennemore wrote: >> >> We have a internal CMDB that gathers facts from systems using the setup >> module on playbook execution. Is there a way to extend the setup module to >> include extra information? >> From what I have read the local facts would work for Linux systems but >> the path wouldn't exist on Windows systems. >> > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/eb517322-44e9-4d7d-aa2b-ea80049b1d1b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
