> 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. >> 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. Thanks for your explanations. cheers pete --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
