Open dpetzel opened 8 years ago
We hit this too. It was especially bad with Active Directory integration. The full Name was not known by us until we added it to Jenkins. (Service account - and casing was different - we didnt enter it into AD). So we saw this firsthand, and just figured out what the full_name was suppose to be.
Just including another use case you might see this.
I am defining a
jenkins_user
as outlined in the readme, and I am seeing the resource is flagged as updated every chef run.NOTE not passing in the
full_name
attributeI've done a little debugging, and here is what I'm seeing when the user has already been created. In the create action there is this check:
Stepping through each of these in sequence we get the following:
Since I've not passed in
full_name
new_resource.full_name isnil
, but current resource has a value, thus evaluating to false. I was able to work around this pretty easily by providing thefull_name
attribute in my recipe, but figured I'd open this for a future fix