Issue #708 has been updated by Robert Scheer.
Luke Kanies wrote: > I just can't see a good way to fix this. Do we update the 'resources' type > so that it knows enough about users to not purge users that should be in > /etc/passwd but aren't? Do we silently ignore any attempt at removing > non-local users? Do we warn on every one? > > I can't see a good behaviour here. If the provider can't add/delete/modify users in other password databases other than the local password file, then the test to see if a user exists should only look in that local file. That way, you completely ignore non-local users and you don't need a way to deal with them. We have the same problems as the creator of related ticket #935: puppet instructs usermod to manipulate users that are not local. That is simply because its test (getpwnam) is wrong. I hope you or Markus can fix this. ---------------------------------------- Feature #708: User and Group providers should directly parse /etc/passwd and /etc/group https://projects.puppetlabs.com/issues/708 Author: Digant Kasundra Status: Accepted Priority: Normal Assignee: Markus Roberts Category: user Target version: unplanned Patch: None Affected Puppet version: 0.25.4rc1 Keywords: Branch: The current user and group providers rely on the Etc module that ships with Ruby to figure out the current state of the system, but that library provides information about users and groups not manageable by Puppet. Instead, the providers should use [[ParsedFile]] to directly parse the appropriate files. -- 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.
