On Mon, Apr 4, 2011 at 1:54 AM, Felix Frank <felix.fr...@alumni.tu-berlin.de
> wrote:
>
>
> On 04/02/2011 08:40 PM, Cody Robertson wrote:
> > It looks like the `user` portion is overriding the original resource? I
> > haven't checked if this would work but maybe you can do something along
> > these lines:
> >
> > Ssh_authorized_key <| title == "test.user.key" |>{
> > user => ["test.user","studio_app"],
> > }
>
> Probably not.
>
> Afaik, an ssh_authorized_key resource is associated with exactly one user.
>
> What you want to do is
> 1. assign your key to a variable ($testkey = "AAAgwiv...")
> 2. declare two ssh_authorized_key resources that both use that variable
> as the "key" parameter.
>
> HTH,
> Felix
>
>
>
Thanks Felix, that worked!
Its interesting that ssh_authorized_keys behaves this way. I would have
thought that having a single key in multiple user's authorized_key files
would have been a use case (albeit a bit unusual)...
--
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.
