On Wed, Feb 2, 2011 at 2:57 PM, Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote: >> Yes: the class statement in the equivalent of "include", as well as >> assigning that metadata. > > ...the workaround being: Use class instead of include in your ruby > manifest (is this available?) and select the desired stage right there.
It's not yet available in the Ruby DSL, unfortunately. It throws an error about the class already existing (example not from amqp:) Duplicate definition: Class[Redis::Main] is already defined at /etc/puppet/manifests/nodes.pp:20 on node puppet (the line number is the puppet file including the ruby file). > Otherwise, define a wrapper-class that sets the stage for your amqp and > include the wrapper class from roles. I guess that works, but what a mess--it's a .pp file for each .rb file. It'll work for now, though. Thanks. > HTH, > Felix > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
