Re: [Puppet Users] Dictating class evaluation order

2015-07-20 Thread Andrew Langhorn
Morning Gareth, Ah - I re-read that, and that makes more sense, especially since renaming the class fixed it. I'll give it a go to neaten up the module; am sure it will work. Thanks both! :) A On Monday, 20 July 2015, Gareth Rushgrove wrote: > Hi Andrew > > On 20 July 2015 at 00:38, Andrew L

Re: [Puppet Users] Dictating class evaluation order

2015-07-20 Thread Gareth Rushgrove
Hi Andrew On 20 July 2015 at 00:38, Andrew Langhorn wrote: > I don't know why, but when I renamed the class, things started to work. > Very odd. Maybe I should just upgrade to the latest stable 3.x release > (3.8.0, I think), or even 4. See Peter's email above. The issue appears to be that you

Re: [Puppet Users] Dictating class evaluation order

2015-07-19 Thread Andrew Langhorn
I don't know why, but when I renamed the class, things started to work. Very odd. Maybe I should just upgrade to the latest stable 3.x release (3.8.0, I think), or even 4. Thanks though - especially helpful on this list, as usual :) On 19 July 2015 at 19:54, Peter Huene wrote: > On Sun, Jul 19,

Re: [Puppet Users] Dictating class evaluation order

2015-07-19 Thread Peter Huene
On Sun, Jul 19, 2015 at 7:07 AM, Andrew Langhorn < andrew.langh...@digital.cabinet-office.gov.uk> wrote: > Hi Felix, > > Thanks for the reply. > > Yep - that snippet is representative. I've copied the full thing for you > below. Granted, it needs some tidying up, but I think it should just work >

Re: [Puppet Users] Dictating class evaluation order

2015-07-19 Thread Andrew Langhorn
I should probably add that, for $reasons, I'm using Puppet 3.6.1. On Sunday, 19 July 2015 15:07:39 UTC+1, Andrew Langhorn wrote: > > Hi Felix, > > Thanks for the reply. > > Yep - that snippet is representative. I've copied the full thing for you > below. Granted, it needs some tidying up, but I t

Re: [Puppet Users] Dictating class evaluation order

2015-07-19 Thread Andrew Langhorn
Hi Felix, Thanks for the reply. Yep - that snippet is representative. I've copied the full thing for you below. Granted, it needs some tidying up, but I think it should just work as it stands: class app::reservations { include tomcat Exec { path => "/usr/bin:/usr/sbin:/bin:/sbin:/usr/loca

Re: [Puppet Users] Dictating class evaluation order

2015-07-18 Thread Felix Frank
On 07/19/2015 01:19 AM, Andrew Langhorn wrote: > > class apps::reservations { > > > include tomcat > > > tomcat::instance { ‘reservations’: > > ensure => present, > > http_port => 8080, > > } > > > } > > > However, when I run Puppet against a

[Puppet Users] Dictating class evaluation order

2015-07-18 Thread Andrew Langhorn
Hi, I have a Puppet manifest which makes use of the tomcat::instance defined type from the camptocamp/tomcat module on the Puppet Forge as follows: class apps::reservations { include tomcat tomcat::instance { ‘reservations’: ensure => present, http_port => 8080, } } However, wh