The subscribe isn't needed if notify is used which is in point 1. There are multiple ways to solve the problem - I prefer pushing these events using notify rather than pulling via subscribe :-)
On 21 March 2013 10:37, Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote: > Hi, > > On 03/14/2013 09:25 AM, Keith Burdis wrote: > > 2) Adding refreshonly => true to the exec. > > > > 3) Remove the creates and subscribe from the exec. > > > > The subscribe is actually fine, but yes - the 'creates' needs to go in > order to allow repeated execution. > > Note that this can be considered unclean manifest design, because > a) notifications can get lost during agent crashes (if you're unlucky) and > b) if the exec fails, puppet will likely not notify again next time, > which is a painful and not at all unlikely failure scenario. > > Ideally, you could construct a "dynamic" creates or unless clause, that > will enable puppet to always infer wether the exec need running or not. > > -- > 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 post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.