Issue #15037 has been updated by Rob Sweet.
Sorry, Nigel. This is the first thing I've tried to contribute on so maybe
I've misunderstood the process. I thought that something with status Accepted
meant that no further discussion was desired.
Chaining an exec seems messy to me but sure, that'd be a workaround.
In the broader scope, has anyone discussed the concept of passing options to
parameters? Seems you could use a construct like this:
<pre>
user { "foo":
...
password => { :value => 'supersecretpassword', :create_only => true },
}
</pre>
Supporting something like that would open the door to various kinds of
sophisticated property/parameter behavior, which could maybe help slim down
manifests a bit.
That said, I definitely don't know the Puppet codebase well enough yet to
attempt coding that kind of broad functionality. And here I thought I'd picked
up something relatively easy to start with. ;)
----------------------------------------
Feature #15037: ability to set initial user password
https://projects.puppetlabs.com/issues/15037#change-71659
Author: Darin Perusich
Status: Accepted
Priority: Normal
Assignee: Rob Sweet
Category: user
Target version:
Affected Puppet version:
Keywords:
Branch:
Add functionality to the *user* type so one can set an initial password to be
set upon account creation. Currently when puppet is managing a users password,
if said password is changed puppet will reset it to whatever value has been
configured.
This is a rehash of http://projects.puppetlabs.com/issues/2046
--
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.
