On Feb 7, 7:33 am, Felix Frank <felix.fr...@alumni.tu-berlin.de>
wrote:
> Hi,
>
> On 02/07/2012 01:56 PM, jimbob palmer wrote:
>
> >> sorry for jumping to conclusions, but your questions suggest that you're
> >> > committed to some rather horribly design ideas.
> > Then please educate me! What's horrible about it?
>
> There are few use cases for parameterized classes, and also few for
> inheritance. Combining them could be considered an advanced concept.
> There is nothing here that suggests you need either technique.
+1
> >> > Can you add some meat to your inquiry? What are your trying to achieve?
> > I have a class which represents a group of yum repositories
> > (something::blah) and that class calls each repository
> > (something::aaa)
>
> You probably want to create a custom type like
>
> define my_yum_repo($url) {
> yum_repo { $name: ...
>
> }
>
> Then you can use it like this:
>
> class something {
> my_yum_repo {
> "internal_repo1": url => "http://...";;
> "internal_repo2": ... ;
> }
>
> }
I have a class much like that in my own configuration, in fact.
Addressing the question more generally, do not use class inheritance
where what you really want is composition. That is, given
class foo::common {
# common stuff
}
use this:
# The right way
class foo::specific {
include 'foo::common'
# specific stuff
}
instead of this:
# DONT DO THIS
class foo::specific inherits 'foo::common' {
}
And definitely do not use inheritance to try to indicate ownership or
some similar concept -- that's alien to Puppet. Puppet has namespaces
and scopes, but no native concept of class or resource ownership, and
all declarations are globally visible once they are parsed.
John
--
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.
