Jeroen van Meeuwen schrieb: > David Schmitt wrote: >> Or 4) provide a ssh::config type that can manage setting values in the >> sshd_config. >> > > Good point. This however is mutually exclusive with managing the file > resource.
Yes. Still, I don't care much about the file-resource-distribution part, since -- through purging -- this can be totally emulated by per-setting resources. e.g. by stuffing all relevant settings into a class. >> 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. >> > > Exporting and collecting resources requires storeconfig capabilities > from the puppetmaster, doesn't it? Yes. And that's still experimental. And sshd_config is probably not the best example for use-cases of export/collect. The global ssh_config is probably a much better one in this case. Think each server distributing its own ssh_config "snippet". 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 -~----------~----~----~----~------~----~------~--~---
