[Puppet v3.1.0 both on the master and client (debian squeeze)]
So, I'm porting a pretty monolithic module over from our 2.6.x puppet
environment to a new puppet 3.1.0 environment and ran into some
notifications in syslog from the puppetmaster.
I have a module/class that instantiates numerous parameterized subclasses.
class my_class {
class {"my_class::some_implementation::parameterized_subclass":
somevariable => true,
}
...
}
and...
class my_class::some_implementation::parameterized_subclass ($somevariable
= false) {
#do stuff
}
So, all works fine, but I get scope & qualified variable notifications on
the puppetmaster. If I change my_class::parameterized_subclass to the
following, it goes away.
class my_class::some_implementation::parameterized_subclass
($my_class::parameterized_subclass::some_implementation::parameterized_subclass::somevariable
= false) { }
That seems a bit bizarre to me (and annoying). Is there a scope behavior
I'm missing that would prevent this type of class layout? Any ideas?
Think of a layout like:
base::security::ossec
base::monitoring::rsyslog
base::monitoring::munin
etc...
Regards,
-Matt
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
