Fantastic. Thank you very much guys.
On Sat, Feb 26, 2011 at 3:42 PM, Nick Fagerlund
wrote:
> Dammit, I hit send by accident. Anyway, the point of this is that
> Nan's method is still doing lookup across classes instead of strictly
> controlling the parent scopes, and I think building this as a
Dammit, I hit send by accident. Anyway, the point of this is that
Nan's method is still doing lookup across classes instead of strictly
controlling the parent scopes, and I think building this as a strict
cascade where everything only looks to its direct parent is going to
get you closer to thinki
Hey, Mohamed. Nan's got a good suggestion; I' Alternately, you could
do this:
node default {
include $perhost_module
# Do nothing else.
}
class some_host_module {
$auth_aaa = "something"
$other_variable = "something"
include class_that_includes_everything
}
class class_that_i
On Fri, Feb 25, 2011 at 3:25 PM, Mohamed Lrhazi wrote:
> Thanks a lot Nick for the detailed response. Not sure I fully
> understand yet. I dont think I can use option one because the external
> classifier would does not have access to the clients facts. I will
> read about parametrized classes and
Thanks a lot Nick for the detailed response. Not sure I fully
understand yet. I dont think I can use option one because the external
classifier would does not have access to the clients facts. I will
read about parametrized classes and learn to use them, though I dont
yet see how they can solve my
Yeah, that's probably not going to get you where you need to be.
Scope in Puppet goes like this:
* When you declare a variable in a scope, it is local to that scope.
* Every scope has one and only one "parent scope."
* If it's a class or node that inherits from a base class/node,
its parent s
