Jira (PUP-8404) ssh_authorized_key should mention effective uid on debug output

[Leo Antunes (JIRA)]

Title: Message Title

Leo Antunes created an issue   Puppet / PUP-8404 ssh_authorized_key should mention effective uid on debug output Issue Type: Improvement Assignee: Leo Antunes Components: Types and Providers Created: 2018/01/30 6:08 AM Environment: linux Priority: Trivial Reporter: Leo Antunes Puppet Version: 4.10.9 Puppet Server Version: 2.8.0 OS Name/Version: linux Trying to use ssh_authorized_key when the parent folder of .ssh doesn't belong to the target user leads to a slightly misleading "permission denied" error during mkdir. This happens because ssh_authorized_key runs mkdir as the target user, which might not be directly clear. Especially since it's not the same behaviour as an explicit file resource with owner set to the same target user (create as root than chown to target user). Desired Behavior: Output of puppet run with --debug: Debug: Creating /somefolder/.ssh as someuser Error: /Stage[main]/Main/Ssh_authorized_key[someuser]: Could not evaluate: Permission denied @ dir_s_mkdir - /somefolder/.ssh Actual Behavior: Output of puppet run with --debug: Debug: Creating /somefolder/.ssh Error: /Stage[main]/Main/Ssh_authorized_key[someuser]: Could not evaluate: Permission denied @ dir_s_mkdir - /somefolder/.ssh Add Comment   This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.