Issue #1581 has been updated by Garrett Honeycutt.
We should not require that a user be managed, in order to manage ssh_authorized_keys. They are very distinct resources and should not be tightly coupled. A real world example, you manage users with a directory, not your puppet code, but still want to ensure state of given keys. ---------------------------------------- Feature #1581: Ability to purge .ssh/authorized_keys https://projects.puppetlabs.com/issues/1581#change-75174 Author: Lars Volker Status: Accepted Priority: Normal Assignee: eric sorenson Category: ssh Target version: Affected Puppet version: 0.24.4 Keywords: Branch: As I'm new to puppet i'll try to describe this as good as i can. I wanted to use the ssh_authorized_key type to add keys to ssh. After a discussion on irc i was suggested to use virtual resources and realize each key for each class needed. This worked well for me. However i am not able to purge all other keys from the authorized_keys file without either specifying the comment or by copying an empty file there before adding the keys, which causes the system to lock up until the update is done. I tried using resources{} type, but as ssh_authorized_key doesn't support "self.instances" this was also of no success. The feature i'd like to have is an implementation of "instances" so resources{} works for authorized_keys. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
