Where do you store your own snippets?

[Dave Augustus]

I started putting mine in /var/lib/cobbler/snippets

But then I saw chatter on IRC about other possibilities.

Would /var/lib/cobbler/local_snippets be best?


Thanks!
Dave

[Michael DeHaan]

Dave Augustus wrote:
>  I started putting mine in /var/lib/cobbler/snippets
>
>  But then I saw chatter on IRC about other possibilities.
>
>  Would /var/lib/cobbler/local_snippets be best?
>
>
>  Thanks!
>  Dave
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
No.

/var/lib/cobbler/snippets is the default path. If you move this path in 
settings, you will disable the cobbler snippets that we package.

If you want, you can namespace snippets though.

/var/lib/cobbler/snippets/acmecorp/foo # is your snippet
/var/lib/cobbler/snippets/network_config # is a stock cobbler snippet

This allows them to be addressed as

$SNIPPET('acmecorp/foo')
$SNIPPET('network_config')

The only real reason to do that would be worrying about if cobbler would 
later add a snippet that would clobber your namespace, in which case
RPM would give you a .rpmsave file, so I'm not so sure that's much of a 
problem.

I would just use the default location and namespace them if needed. 
Multiple levels of nesting are fine if you want to have them.

--Michael

[Dave Augustus]

On Thu, 2008-09-25 at 15:43 -0400, Michael DeHaan wrote:
>  $SNIPPET('acmecorp/foo')
>  $SNIPPET('network_config') 
for kickstarts, is this the proper syntax ?

Dave

[Michael DeHaan]

Dave Augustus wrote:
>  On Thu, 2008-09-25 at 15:43 -0400, Michael DeHaan wrote:
>    
> > $SNIPPET('acmecorp/foo')
> > $SNIPPET('network_config')
> >     
>
>  for kickstarts, is this the proper syntax ?
>
>  Dave
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
Works in 1.2.X and later.

You are probably used to "SNIPPET::foo/blah"

also works for legacy reasons, though I like the form that implies it's 
Cheetah syntax code, which it now is, so that's why I used that.

Both will continue to work.

--Michael