Issue #6059 has been updated by Nigel Kersten. Status changed from Needs Decision to Rejected
Roles aren't full users, and I don't believe that they support the shadow file semantics that are needed for password ages. ---------------------------------------- Feature #6059: password_max_age & password_min_age should work on solaris role https://projects.puppetlabs.com/issues/6059 Author: Merritt Krakowitzer Status: Rejected Priority: Low Assignee: Nigel Kersten Category: Target version: Affected Puppet version: 2.6.4 Keywords: Branch: user { "foo": gid => 'sysadmin', uid => '1501', ensure => 'role', profiles => 'Primary Administrator', password_max_age => '30', password_min_age => '1', } when I run puppet: <pre> err: /Stage[main]/Unixadm_role/User[foo]/password_min_age: change from 7 to 1 failed: No command role_password defined for provider err: /Stage[main]/Unixadm_role/User[foo]/password_max_age: change from 56 to 30 failed: No command role_password defined for provider </pre> -- 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.
