hello,
> The problem with this structure is the possible (silent!) parse-order
>
> dependence of this node:
>
> node broken {
> include roles::web_node
> include roles::another_node_type
> }
>
> The "lexical" model would either resort to extlookup:
>
> node web1, web2 {
> $apache::procs = extlookup("apache::procs", 10, "web_nodes")
> include web_node
> }
>
> or node-inheritance:
>
> node web {
> $apache::start_procs = 10
> include apache
> }
>
> node web1, web2 inherits web {
> }
>
>
> Especially the latter is only a minor change and (by using single
> inheritance) correctly asserts that a node can only have "one"
> identity
> (source of configuration variables).
I am not totally convinced about something that forces the use of inheritance
to get things sane, sure this change will at least "fix" node inheritance and I
agree I'd rather use extlookup there but not everyones seen the light on this
kind of thing yet :)
Really if you use role classes you most certainly will not be including both so
the silent failure you suggest just wont happen in this specific case.
--
R.I.Pienaar
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
