On Wed, Oct 24, 2012 at 2:28 AM, Lukas Hetzenecker
<lukas.hetzenec...@gmail.com> wrote:
> Hello,
>
> I am a big fan of Puppet (btw, congratulations to your 3.0 release), but
> there was always one thing that bothered me: the imperfect handling of the
> authorized_keys of SSH.
> To support more than one local user account for one SSH user some ugly
> workarounds were needed.
>
> So I decided to fix this issue and published my attempt here:
>
> https://github.com/lukas-hetzenecker/puppet-module-ssh_authorized_key
>
> The module allows you to specify an array for the user or target attributes
> and uses the SSH key fingerprint as resource identifier (optionally the
> comment can be made unique too).
> This should fix the issues mentioned in bug #1531 (
> http://projects.puppetlabs.com/issues/1531 )
>
> Please note that this module is my first experience with Ruby and Puppet
> module development, so it may contain bad code. Therefore I'm glad about any
> feedback you give me about this code.

Thanks for sharing your module!

You might get some additional feedback if you also upload your module
to the Forge: http://forge.puppetlabs.com/

Here's a link to the how-to for publishing a module on the forge:
http://docs.puppetlabs.com/puppet/2.7/reference/modules_publishing.html

Dawn

-- 
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 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to