On Oct 2, 2008, at 10:37 PM, qbert980 wrote: > > I'm probably not understanding how facts work, but I'm hoping that > somehow if a fact gets loaded by the puppetmaster, it could be used as > a variable by all puppet clients, but this is turning out not to be > the case. > > On my puppetmaster, I've got a ruby script that parses a simple text > file located on the puppetmaster to load <somevariable>. However when > I run puppet on the client it wants to download the ruby file that > parses the fact rather than the fact itself, so puppet errors out > saying that the template cannot be parsed since it cannot find > <somevariable>. > > Currently my facts are separate from my modules, and I've got the > correct settings in my fileserver.conf file (I think), as the > puppetmaster parses the fact just fine, so I don't think the facts > being separate from the module is the problem, as I've tried it with > the fact embedded in the module as well. > > Is there some simple "fact" that I'm overlooking. To paraphrase Joe > Friday, I want just the facts man. . . just the facts.
Sounds like you should be using a custom function rather than a fact -- these only run on the server, and are perfect for doing things like parsing data files that only exist on the server. -- Reality is that which, when you stop believing in it, doesn't go away. -- Philip K. Dick, "How to Build a Universe" --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
