On Oct 11, 5:45 pm, Scott Smith <sc...@ohlol.net> wrote: > One word: Idempotence. > > If you have to do what you are asking, ur doin' it wrong.
Weeel,,not neccessarily. It can still be "Idempotent". The 'state' we wish to maintain, can be, "machine has a self-generated/updated entry in central database, that is no older than X number of hours". So after the first successful run, it will not fully trigger again, until after X number of hours. And that's fine. BUUT... maybe I am thinking about this all wrong after all. Possibly the better way is to give facter a custom set of facts... and then since facter output gets automatically stored on the master when puppet runs on the client, that would be a better source for the repository...? Hmm.... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
