Jeff Schroeder wrote:
On Fri, Mar 20, 2009 at 9:33 AM, Michael DeHaan mdehaan@redhat.com wrote:
Pre-triggers (as compared to post triggers) were intended to reject additions to cobbler's "DB" if the input wasn't any good.
I would speculate no one is using them and this would simply some things if they went away.
Just curious. If we did this it would be done in 1.8
I'd planned on adding pre triggers to add forward/reverse dns records to a certain vendor's[1] dns appliances via xmlrpc. The idea would be that adding a system into cobbler with the --dns-name info for an interface would update your dns information. If you're going to remove the functionality I should forget the idea though.
That's fine, that's what I wanted to know.
Basically I don't really need to remove it -- but I do want to say that manipulating the cobbler API from a pre trigger should be off limits.
This eliminates a place where we have to reload the config.
--Michael