hello, At present the reports are sent after the post command is run. I don't understand why this is the case and wondered if anyone know if this was a deliberate decision?
I'd like reports to be written first so I can do something with them in the post command at present I am always lagging one run behind. I can take a stab at swapping these around and sending patches but wondered if anyone knew of a reason that would be a bad idea. This happens in Configurer#run Another option for me would be if there was some way to have node side reports processor? I couldnt find anything in Puppet that has that but might have missed some subtle config tweak. My use case is that I really do not want to process reports on the masters I want them done on nodes and I want just bits pulled out of them - just the resources thats changed for now. I send this into my event system where I have callbacks that gets fired soon as these events come in. So I have network wide callbacks for lets say a new webserver coming online I can immediately trigger puppet runs to configure load balancers via mcollective. This lets me converge changes throughout the network real quick but I need a way to get the events. -- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
