Closed asciifaceman closed 8 years ago
Also, apologies if I missed the naming convention for the pull/commit. I read the guidelines after pushing them to my fork and pull requesting (I am a terrible example for society).
have created a new PR to supersede this - see https://github.com/opscode-cookbooks/users/pull/90
handles things a bit nicer, using file resources.
Cool!
Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.
As this has been superceded by https://github.com/chef-cookbooks/users/pull/90, and by non-github verified committers, I'm going to go ahead and close this pull request. Please reopen if you don't think https://github.com/chef-cookbooks/users/pull/90 will solve your needs. Thank you.
If all ssh keys are removed but not the user itself chef was not zeroing-out the authorized_keys file. This behavior is desirable if you are on a key-only auth system with no SUDO and you remove the user's ssh keys but do not want to wipe out the user entirely. Currently, if you remove all ssh keys from the data bag it never touches the authorized_keys file instead of updating it to represent the changes (IE zeroed-out)