Not sure if this will work as expected for your custom type, but a thought might be to set some (provider) class variable in #flush and then, in ::post_resource_eval, check if this variable is set and do the restart (so each flush does no actual work other than setting the flag).
Eric On Thursday, March 6, 2014 1:23:39 PM UTC-6, Stefan Schulte wrote: > > Hi Erik, > > On 06.03.2014 09:28, Erik Dalén wrote: > > Isn't this what was done in http://projects.puppetlabs.com/issues/3946? > > So should be available in 3.4.0+ > > > > Was discussed in this mail > > thread: https://groups.google.com/forum/#!topic/puppet-dev/Iqs5jEGfu_0 > > thanks for finding the ticket and pull request for me. I have looked > into the implementation but if am not mistaken `post_resource_eval` will > be called on every puppet run (after all resources are evaluated) no > matter whether resources where out of sync or not. > > This is not quite what I want, because I only want to restart my > application when one ore more resources have been changed. > > -Stefan > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev/c02cf41d-c30a-491c-970c-2c5d0f9d0a92%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
