On Jun 7, 3:23 am, Felix Frank <[email protected]> wrote: > On 06/07/2012 10:18 AM, Walter Heck wrote: > > > The other option is to move the include virtual to inside the > > user::developers class. > > > On Thu, Jun 7, 2012 at 9:11 AM, Walter Heck <[email protected]> wrote: > >> > We usually choose to inherit the developers class from the virtual > >> > class, have you tried that approach? > > Are you implying a parse order dependency? > > That should not be the case. I've yet to see any evidence for this > happening. > > The theory is: If a virtual resource X is declared *anywhere* in a given > node's manifest, realizing it will add it to the catalog.
Does that suppose that the realize function enqueues a command to be processed later, to perform the actual realization after everything has been parsed? I don't think that's the way it works. Yes, the virtual resource can be declared anywhere, but its declaration needs to have been parsed before the resource can be realized. Personally, I would put "include 'user::virtual'" at the beginning of the body of class user::developers to address that requirement. I do not think it's a parse-order issue, however. In the first place, Puppet should emit an error message if instructed to realize an (at that point) unknown resource. In the second place, the node declaration includes user::virtual before user::developers, so they should be parsed in that order. I'm with Felix in thinking that there is some missing or incorrect information here. The output from "puppet agent --debug --no- daemonize --onetime" might help clarify things. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
