Is anyone using "pre" triggers?

[Michael DeHaan]

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

--Michael

[Jasper Capel]

On 03/20/2009 05:33 PM, Michael DeHaan 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 think we might be, to erase a system from Puppet-CA and/or
Certmaster-CA. This is the trigger that runs from the wget in %pre, right?

Jasper

[Michael DeHaan]

Jasper Capel wrote:
>  On 03/20/2009 05:33 PM, Michael DeHaan 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 think we might be, to erase a system from Puppet-CA and/or
>  Certmaster-CA. This is the trigger that runs from the wget in %pre, right?
>
>  Jasper
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
Sorry, wrong kind of pre.

Like "system/add/pre" and "system/add/post"

These are API level triggers that fire when objects are modified, not 
install time time triggers.

--Michael

[Jeff Schroeder]

On Fri, Mar 20, 2009 at 9:33 AM, Michael DeHaan <mdehaan(a)redhat.com&gt; 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.

[1] http://www.bluecatnetworks.com/

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

[Michael DeHaan]

Jeff Schroeder wrote:
>  On Fri, Mar 20, 2009 at 9:33 AM, Michael DeHaan
> <mdehaan(a)redhat.com&gt; 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.
>
>  [1] http://www.bluecatnetworks.com/
>
>     
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