Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Done
-
PUP 3.7.3
-
None
-
Windows 2008 R2, Windows 2012, Windows 2012 R2
-
2
-
Windows 2015-04-08, Windows 2015-04-22
-
Bug Fix
Description
In Windows, many groups are built-in and cannot be removed, therefore ensure => absent is useless. Another approach would be to define the group as present with no members. For example:
group { 'Guests':
|
ensure => 'present',
|
members => [],
|
}
|
Unfortunately, this will not remove any members of the built-in Guests group, but instead leave any members existing.
The underlying goal is to ensure that all unnecessary groups are empty.
Update for Puppet 4
In PUP 4.x+, because groups are not authoritative by default, you need the add auth_membership => true to the mix to force an existing group to empty.
group { 'Guests':
|
ensure => 'present',
|
members => [],
|
auth_membership => true,
|
}
|
Attachments
Issue Links
- relates to
-
DOCUMENT-356 confusing documentation of *_membership attributes of group resource
-
- Closed
-
-
PUP-4396 Group Created when "members" Parameter Contains Invalid User
-
- Closed
-
-
PUP-4373 Windows ADSI User groups property should behave similarly to Groups members property
-
- Closed
-
-
PUP-2628 Ability to add a member to a group, instead of specifying the complete list
-
- Closed
-
-
PUP-3719 Group resource non-authoritative by default (Breaking change)
-
- Closed
-
- links to