On Thu, 12 May 2011 09:59:21 +0200
Felix Frank wrote:
> On 05/11/2011 05:36 PM, Arnau Bria wrote:
> >> If you're keen to get it anyway, you may want to open a ticket.
> > I think I've already asked here... but I have an example where that
> > feature is really interesting: we have some user pool, aout 1000
> > users, and I'd like to distrbute one key to all those users. Why the
> > trivial workaround, I could do it, but with 1000 lines :-)
>
> That's just not true.
>
> You surely have some defined type for your users, no? Such as
Nop, we use an other software for creating those users.
So, I must redefine each key for each user, and then my problem
appears.
[...]
> my_user($fullname) {
> user { "$name": fullname => $fullname, ... }
> ssh_authorized_key { "key-for-$name":
> user => $name,
> key => "AAznbwet...",
> ...
> }
> }
> That's what I meant - the workaround is really *that* trivial.
>
> I'm quite sure you'll have a hard time finding a use case that really
> requires the authorized key resource to be effective for multiple
> target users.
>From your example I think I can play with a false define for something
else trivial and add my key there....
> Regards,
> Felix
Cheers,
Arnau
--
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.
