On Thursday, May 7, 2015 at 11:22:43 PM UTC-5, Alfredo De Luca wrote: > > Hi John. > I am aware that if I say userxx ensure is present will work but what I > want is the first time create the user aNd set a default password but then > when the user changes it own pass I just wanna check if is present and not > resetting the password. >
Then as I said, create and use a custom fact to evaluate the user's existence prior to the catalog request. Also, consider configuring agents to not apply cached catalogs. You could perhaps create a custom provider for the User type, too, to perform the evaluation at the time of application. That could work to achieve the behavior you describe, but it will probably produce anomolies in the form of reported updates to the affected user(s) that in fact change nothing. John -- 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/d22f7a8d-b29e-408d-9351-ad088349be1d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
