It must be some kind of "sales department" decision, you name things to be attractive, not because they represent reality.
On Tuesday 06 March 2012 05:53:57 chris_sny...@sra.com wrote: > I don't understand Puppet Language. How can you take object-oriented > constructs such as 'class' and 'inheritance' and then not allow things like > multiple instances of a class, albeit with differing parameters. Defined > resource types don't help me as they don't have inheritance (which is > something I very much want). > > On Monday, March 5, 2012 4:13:30 PM UTC-5, denmat wrote: > > Hi, > > Here's what the docs say: > > > > "Okay, we can pass parameters into classes now and change their > > behavior. > > Great! But classes are still always singletons; you can’t declare more > > than one copy and get two different sets of behavior simultaneously. > > And you’ll eventually want to do that! What if you had a collection of > > resources that created a vhost definition for a web server, or cloned a > > Git repository, or managed a user account complete with group, SSH key, > > home directory contents, sudoers entry, and .bashrc/.vimrc/etc. files? > > What if you wanted more than one Git repo, user account, or vhost on a > > single machine? > > > > Well, you’d whip up a defined resource > > type<http://docs.puppetlabs.com/learning/definedtypes.html> ." > > > > So have a look at changing the bar class to a define instead. > > > > Cheers, > > > > Den -- 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.
