Hi, On 01/26/2012 08:14 PM, Jo Rhett wrote: > One thing about a well-written piece of generic code is that it can be used > in many environments. A lot of my modules do things like "do I have an > external interface or am I behind the firewall?" and do different things > based on those answers. Likewise, when dealing with software components you > could be on a system dedicated to just that one component, or you could be on > a Dev/QA box which has dozens of such components installed. The behavior > calls for different actions there.
what about custom facts, then? On 01/26/2012 08:22 PM, Jo Rhett wrote: > You can't import because of redefinitions. You yourself know well and deeply the issues involved with calling the same class from different places with different parameters. It is nearly impossible to get there from here. Have you considered combining class inheritance with parameters? I have found that in many situations, it's extremely helpful to be able to include an unparameterized base class to satisfy dependencies, and allow nodes to include additional subclasses that take care of the gory details. Granted, this approach won't float any boat out there, but potentially helpful in the SSH example you gave. Cheers, Felix -- 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.
