Thank you all for your responses. >From John's response, I see that I'm going to struggle here. Ultimately, I am just trying to get some details about the system, and will look into installing our system info script as part of the OS build. Truthfully though, it's not doing so much that I couldn't just write it in Ruby and have it run during the fact gathering stage of the initial puppet run. I would have liked to avoid this though, as it means the same functionality will live in two places. I guess one day the binary could just be reporting facts rather than being the source of truth itself. It's not so terrible to do this, but it's a shame I can't just integrate Puppet with my world, but instead have to make the world integrate with puppet.
This could all be solved if there was a way to make Puppet re-evaluate facts either on request during a module's execution, or to have them evaluated on first use (after all, they are written as "fact name = X, code to execute to get its value = Y"), or some other means. Does any of this sound like desirable behaviour or worth taking it up with Puppetlabs for the future? ...Ralph -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c74cc3f8-92de-4d80-9b75-c3445651cd2d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
