Re: [Puppet Users] Re: Problems with require inside a definition

2010-08-10 Thread Jason Koppe
Yes, that's part of the reason. I was working on my module at an obscene hour and that probably factors in to my extra require dance. On Tue, Aug 10, 2010 at 10:39 AM, Nigel Kersten wrote: > Argh. Everyone is doing this require dance because of the docs on > definitions right? > > http://docs.p

Re: [Puppet Users] Re: Problems with require inside a definition

2010-08-10 Thread Nigel Kersten
Argh. Everyone is doing this require dance because of the docs on definitions right? http://docs.puppetlabs.com/guides/language_tutorial.html#definitions We had a chat about that on the list a while ago and realized that was horribly out of date, I'll try to get a patch in to fix it. On Tue, A

Re: [Puppet Users] Re: Problems with require inside a definition

2010-08-10 Thread Jason Koppe
Thanks, that works as expected. On Sun, Aug 8, 2010 at 4:58 PM, Peter Meier wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 08/07/2010 01:31 AM, Jason Koppe wrote: > > I ended up getting this syntax to work: > > just minor note: > > > > 4 $id, > > 5

Re: [Puppet Users] Re: Problems with require inside a definition

2010-08-08 Thread Peter Meier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/07/2010 01:31 AM, Jason Koppe wrote: > I ended up getting this syntax to work: just minor note: > 4 $id, > 5 $runlevels = '123456', > 6 $action = 'respawn', > 7 $process

Re: [Puppet Users] Re: Problems with require inside a definition

2010-08-06 Thread Jason Koppe
Just in case anyone searches on some keywords in this thread, I feel it only appropriate to put the final, working manifests here. Note that the environment variable in Exec['install supervisor'] changed to lower case and the set for $id/process in the define uses quotes around the value since the

Re: [Puppet Users] Re: Problems with require inside a definition

2010-08-06 Thread Jason Koppe
I ended up getting this syntax to work: Here is the class calling the define: 2 class supervisor { ... 13 exec{"install supervisor": ... 32 33 # running 'init a' will start supervisord -- should be called at the end of /etc/init.d/Indeed to start tomcats after slaving/caching

Re: [Puppet Users] Re: Problems with require inside a definition

2010-08-06 Thread Jason Koppe
If you just mean this: 1 # generic class to allow /etc/inittab management 2 class inittab { 3 define conf ( 4 $id, 5 $runlevels = '123456', 6 $action = 'respawn', 7 $process 8 ) { 9 $r

Re: [Puppet Users] Re: Problems with require inside a definition

2010-08-06 Thread Jason Koppe
I'm having similar problems, should it be: class inittab { define conf ( $id, $runlevels = '123456', $action = 'respawn', $process ) { $require { $require }

[Puppet Users] Re: Problems with require inside a definition

2010-07-12 Thread Tim
Thanks, that fixed it. On Jul 9, 5:10 pm, Alan Barrett wrote: > On Fri, 09 Jul 2010, Tim wrote: > > # Generic config file > > define config-file ($fullpath, $source) { > >         if $require { > >                 require $require > >         } > >         file { $fullpath: > >         source =>