On Tue, Jan 20, 2015 at 9:40 AM, jcbollinger <[email protected]> wrote: > There seems to be a bit of a terminology gap here. Class['a'] does not > "have" a service.pp in any useful sense of the term. I suppose you probably > mean that module 'a' has a class or defined type "a::service" whose > definition resides in modules/a/manifests/service.pp. The distinction > matters, as does, in particular, whether a::service is a class or a defined > type. (In a typical module architecture, such a thing would be a class.)
Yes, that is correct. Sorry for my lack of proper terminology. > Moreover, it's unclear what you mean when you say you "use the anchor method > on the Service Type [...]." I can probably guess roughly what you mean, but > here, too, the details matter. We can give better answers if you present > code that actually exhibits the problem -- preferrably minimal code that > does so. Point taken. > My best guess at this point is that you have a class containment issue. > That is, Puppet is very likely applying the ordering you specify, but that > doesn't have the effect you expect because Class['a'] and/or Class['b'] > declares other classes that you consider as belonging to 'a' / 'b', but > which are not properly contained by 'a' / 'b'. Thanks for the link. This does sound like what is going on. I'll take a look at the module and see if this will help. Thanks, -- Jason Wever -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEqBX788SiCn6-9butPtn-mbXhSky8vSL5Mxf4m8778FgiYZ4w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
