-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chef_user isn't fully idempotent due to password attribute #83
Comments
Note: this is being run as pivotal. |
We need to separate this into two bugs:
|
@jkeiser Was any progress made on trying to solve |
"Cannot create a user without a password" feels like a feature not a bug. What about feeding it a string of 32 randomly generated characters? |
Setting as reasonably high since we shouldn't crash. |
We probably should at least error out better on the client rather than relying on the server to 400. |
#106 has much better information on this -- the problem is related to trying to update the user, likely due to the server using a RESTful verb model, while the password has been one-way hashed so that doing a GET+POST doesn't work. The server should probably be changed to not require the password field on a POST and be "patchier". |
The chef_user will not work unless I specify
:password
attribute. I'll get 400 bad request error if I try to comment attribute out.However even though the user is already created it keeps trying to update password in sequential chef-client runs. I can not get this resource to skip and report (update to date).
I noticed related comment here, so maybe known already, but didn't see any issue reported on this.
https://github.com/chef/cheffish/blob/master/lib/chef/resource/chef_user.rb#L25
The text was updated successfully, but these errors were encountered: