Hi,
I've been bitten by this quite a few times now, so it got me
wondering...
When I have both the following classes available :
nagios::client
mycompany::nagios::client
And I decide to "include nagios::client", things get weird. What I've
seen is that even if it's from the top scope, puppet can get confused,
which in turn gets me confused : From inside the "mycompany" module, I
could understand the ambiguity, but from outside it doesn't make much
sense (this is with puppet 3.1.1).
Anyway, what does seem to always work is this :
include ::nagios::client
and of course, this also :
class { '::mycompany::nagios::client': ... }
And given how puppet's variable scoping works, it makes most sense. But
this fully qualified class name syntax isn't present in the
documentation[1][2], so I'm wondering :
Is this the proper syntax?
Has this (or will this) become the best practice?
Matthias
[1] http://docs.puppetlabs.com/puppet/2.7/reference/lang_classes.html
[2] http://docs.puppetlabs.com/puppet/2.7/reference/lang_scope.html
--
Matthias Saou ██ ██
██ ██
Web: http://matthias.saou.eu/ ██████████████
Mail/XMPP: [email protected] ████ ██████ ████
██████████████████████
GPG: 4096R/E755CC63 ██ ██████████████ ██
8D91 7E2E F048 9C9C 46AF ██ ██ ██ ██
21A9 7A51 7B82 E755 CC63 ████ ████
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
