----- "Peter Meier" <[email protected]> wrote:
> > This would essentially be a run-many-times-till-it-works approach > > rather than a clean dependency based solution, unless you put in a > > lot of before => properties in these classes, and this too would not > really do it properly. > > agree. But I have to admit, that I would simply order the things > different to avoid that. yeah, the main issue here is modules from something like common modules, or people like me who has a core set of modules in use by many clients. but as clients need change I need a way to put in site specific differences. > > >> I'm not (yet ;) ) really arguing against your proposed solution, I'm > >> just trying to understand the problem you'd like to have solved. > > > > > > resources in openvpn::service requires Class["openvpn::config"] and > > this cleanly ensures all config happens before the service happens, > > I think is essential in achieving the goal of sharing modules that > > are not just configurable but also extendable to local needs > > right, I see it now. Actually I usually don't specify dependencies on > class level, as I would order it anyway different. But I see that for > the way you are doing the class setups you would need that. If you're writing modules for many distributions, or complex ones with lots resources per class, you can't just say: notify => Service["apache2"] or require => File["/etc/apache2/conf.d/foo"] Because redhat has Service["httpd"] and so forth and so on, if the OS specific code is in apache::service I can just do notify => Class["apache::service"] and it will always do the right thing, Same I wouldn't want to maintain a huge require list for files - and I wouldnt know what the operating systems do, requiring the class solves that problem. Same for requires etc, I wrote more about the structure and needs for it here http://www.devco.net/archives/2009/09/28/simple_puppet_module_structure.php -- R.I.Pienaar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
