Looking through the source on my server (version 2.0.3.1), the triggers are passed the name of the object that caused them to run. I've used them in the past, but since we've changed the way we deploy, I haven't in couple years.
On Fri, Aug 5, 2011 at 10:26 AM, Stuart Sears <[email protected]> wrote: > Hi, list! > > So, after replying to Paul's question about ksmeta variables, I decided > to experiment with creating a trigger to render a custom per_system > snippet with ks metadata args, for reporting if nothing else. > > This page has been helpful (and should be linked from the cobbler wiki > IMO. So I have :): > > http://www.ithiriel.com/content/2010/03/29/writing-install-triggers-cobbler > > So I tried something similar to the above as a pure python trigger, but > this eventually, after much facepalming, exposed that 'change' triggers > appear to be called with no args whatsoever, so I am unable to determine > what precisely has been changed. > > Why would this be? By design? > Am I completely misunderstanding them? > > If I wanted, for example to record the changes made to ksmeta etc for > profiles or systems (and possibly other objects), can I do this? > > has anyone successfully used these triggers? > > (Puzzled) Regards > > Stuart Sears > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > -- Benjamin Riggs Systems Staff School of Mathematics 612-625-4895 _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
