In that case just have puppet create the directory if it doesn't already exist and ensure that the ownership is set correctly. Then have the ssh_authorized_keys resource require the directory resource.
On Monday, 4 April 2016 14:23:11 UTC+1, Patrick G. wrote: > > I don't need to create the user just /home/<username>/.ssh because the > user exist in ldap. > So how do I give access to puppet to create only /home/admin/.ssh > > > > Op vrijdag 1 april 2016 16:32:43 UTC+2 schreef Mike Hendon: >> >> >> On Friday, 1 April 2016 14:34:01 UTC+1, jcbollinger wrote: >>> >>> >>> >>> On Thursday, March 31, 2016 at 9:34:04 AM UTC-5, Warron French wrote: >>>> >>>> Isn't .ssh created after the first time a user attempts an SSH outbound >>>> connection, not at initial creation of homedirs? >>>> >>> >>> Inasmuch as we seem to be talking about OpenSSH or a work-alike, yes, >>> the ssh client creates the .ssh/ directory automatically at need. In no >>> way does that mean it cannot or should not be created by another mechanism, >>> however. The directory needs to exist so that Puppet can manage an >>> authorized key entry within. If it does not already exist at the time of >>> the catalog run, then Puppet needs to create it. Puppet is trying to do >>> so, but failing. >>> >>> >>> John >>> >>> >> To create the admin home directory first the ssh key resource should be >> dependent on an admin user resource. >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d40118b0-887a-4324-ad5e-d2e97c878753%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
