That's actually another good point, Doug. It would be awesome to have puppet create users with an initial password hash, but then ignore future changes to the hash (as when a user updates his own password).
I have a feeling that there are a number of situations where it would be nice to have puppet create resources with some initial set of settings, but then ignore when the on-machine configuration diverges from what's configured in puppet. Perhaps this needs a new feature request? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/79803362-86cc-463a-aff5-70c75a08dee0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
