Jira (PUP-1616) catch-22 in dependancy ordering for user and ssh_authorized_key

[Jo Rhett (JIRA)]

Title: Message Title

Jo Rhett commented on an issue   Re: catch-22 in dependancy ordering for user and ssh_authorized_key I am the reporter for this issue, I'd appreciate it if you'd update this in the issue. The only non-tracking comment in the Redmine issue was my own: I’d also like to point out that this problem isn’t just a quiet annoyance. Unless the double-ifed syntax above is used, removal of the user causes a puppet agent run failure report every $runinterval. Add Comment   Puppet / PUP-1616 catch-22 in dependancy ordering for user and ssh_authorized_key In theory, the dependancy of the ssh_authorized_key upon the user makes sense, but in practice it fails. You can't create the ssh_authorized_key until the user exists, check. You can't remove the ssh_authorized_key unless the user fails... fail. There's no simple way to order this such that an ssh key is removed when the user is removed. The onl... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.