Issue #708 has been updated by Daniel Pittman.
Description updated
Status changed from Unreviewed to Rejected
I appreciate the desire to manage only local resources, and thus to show only
them, but the definition of "what can be managed" is going to vary enough
site-to-site that we literally *cannot* determine this ahead of time.
As an example, it is quite reasonable for someone using an SQL database backed
NSS and PAM set to manipulate their "local" accounts with Puppet, even though
those are stored in SQL and are absolutely, without question, not present in
`/etc/{passwd,group,shadow}`.
We can't get into the business of whitelisting the "approved" storage forms, so
while I might entertain blacklisting some specific store for a specific
problem, in the general case we are not going to do this on Linux and other
traditional Unix systems that support a full, pluggable NSS system.
----------------------------------------
Feature #708: User and Group providers should directly parse /etc/passwd and
/etc/group
https://projects.puppetlabs.com/issues/708
Author: Digant Kasundra
Status: Rejected
Priority: Normal
Assignee:
Category: user
Target version:
Affected Puppet version:
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.
