>> I actually wish puppet had a 'confine' parameter for classes like it does
>> for custom facts. It would make it easier to avoid shooting yourself in the
>> foot.
Wishes don't get anyone anywhere.
Filed feature requests do however ;)
We've had a few conversations in the past about extending "confine" to
classes as well. It's a reasonably natural syntax for certain use
cases.
>>
>> class foo {
>> confine $kernel => ['Linux', 'Darwin']
>> }
>
>
> I wouldn't have a problem with that, but you can accomplish the same
> thing now with a conditional around the whole class body.
jcbollinger has done a great job outlining the problems that this
automatic disabled-inclusion suggestion poses, and indeed the
conceptual problems with the underlying desire itself.
If you *really* want this you could implement it reasonably easily in
a custom external node classifier, but it's rather unlikely this would
make it into core.
--
Nigel Kersten
Product Manager, Puppet Labs
Join us for PuppetConf
<http://www.bit.ly/puppetconfsig>
Sept 22/23 Portland, Oregon, USA.
--
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.
