Jeroen van Meeuwen schrieb: > Point taken, but the number of configuration options available in any > given application does rise another problem for me; > > How can I use and re-use the same /var/lib/puppet/modules/ssh/ directory > to multiple organizations if I know each of those organizations is going > to mess with every possible setting available in sshd_config? > > In my opinion, you can go three ways: > > 1) Have files put in the right location
> 2) Do templating > 3) Minimize the management or differentiation in the module and require > the user of the module to define either an augeas type for use with the > specific model or override file location settings using subclasses > (which can be done right now as well BTW, so reducing the number of file > sources is not a problem). Or 4) provide a ssh::config type that can manage setting values in the sshd_config. This is the most flexible approach, enabling fun stuff like purging, virtual resources, export/collect and a variety of other scenarios. This also avoids having to use a big set of variables as you outline in your other mail. Of course using augeas in the guts of such a ssh::config type is probably a very good idea in the long-term. Regards, DavidS --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
