Will do. Thanks! Do you by any chance know how notifications are generated by providers? In essence, what tells Puppet that there needs to be a notify? I was looking through the vcsrepo git provider code but did not see anything that looked like it would tell but I am newer to the low level details of providers. If you know where I would start I would be happy to troubleshoot issues with the vcsrepo git provider as they come up.
Thanks, Adrian On Tuesday, October 9, 2012 3:39:48 PM UTC+1, Ramin K wrote: > > On 10/9/2012 7:25 AM, Adrian Webb wrote: > > Are you sure this notify is only triggered when there is an actual > > change in the repo (working copy has changed) or is it when the vcsrepo > > resource is executed like most notify's? > > I don't believe your logic on Puppet notifies is correct. Assuming > the > provider is correctly written a notify should only be generated on a > change like in the case of File, Service, Package, etc. > > In any case, test it first in a few scenarios and make sure. FWIW the > vcsrepo::git provider is low to middling quality and you're likely to > find cases that don't work as expected regardless. > > Ramin > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/5VZKD4bR5bAJ. To post to this group, send email to puppet-users@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.
