On Friday, October 10, 2014 6:29:32 AM UTC-5, ganesh634 wrote: > > The goal it to implement a new resource type that will read the > config file and apply it on device on first client run. > > For subsequent client run the apply action should be done only > if the content of config file is changed. > >
You are trying to re-invent the wheel. Puppet already has a facility for resources to be advised when Puppet creates or updates other resources. It is exposed in the DSL via the 'notify' and 'subscribe' resource metaparameters and the signaling chain operators ~> and <~. If during a run a resource receives any 'events' from modified resources, then the event recipient is 'refreshed' some time after being brought into sync. That facility is commonly used to restart system services when their config files are changed, which seems similar to what you want. The developer docs aren't clear on how a provider for a plug-in type supports refreshing, but probably you just need it to have a particular method (named "refresh" more likely than not). If a plug-in type is what you have in mind, then you might find the Puppet Developers group more helpful. You could also look at the providers for types that support refreshing, especially Service. John -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/573ef611-a296-4883-8e20-d697ac9bf3ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
