Not sure if this was mentioned yet but since many environments ssh key management styles will be different, why not make puppet "auto-require" the resource and have it downloaded before compile time. There could be an official key/value map in order to tell puppet which module to use and where to download. This map could be overridden to suit user's demand. You could then pull stuff out of puppet core and place into puppet forge with a resource map that maps the resource to a puppet module of the users choice. Not sure if this is possible or if it makes sense, but it sounds cool in my head. I see it as a method_missing like functionality for requiring puppet modules.
corey On Thursday, February 14, 2013 7:01:41 AM UTC-8, Lukas Hetzenecker wrote: > > Hi guys, > > i developed a module for puppet that handles the ssh key management in a > saner way. > The biggest shortcomings of the ssh_authorized_key resource are listed in > Puppet bug #1531 and should be fixed with this approach. > > Could a developer have a look at this code? Would it be possible to > include it in a future release of Puppet? > > It is available here: > https://github.com/lukas-hetzenecker/puppet-module-ssh_authorized_key > > Greetings, > Lukas Hetzenecker > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To post to this group, send email to puppet-dev@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
