update manpages for version bump to beta 1
the set_unless state is bleeding from call to call...
also clear set_unless_present in reset_cache
specs to test for set_unless flag badness
[CHEF-3806] add attribute value debug
[CHEF-3806] add tests for "dangling" set_unless state bleed
Merge branch 'set-unless-fix'
bump rack (test dep) to silence warnings
use make_tmpname to avoid finalizer races
make nil the default for second argument of make_tmpname()
Merge branch 'tempfile-finalizer-races'
version bump to 11.0.0.beta.2, regen docs
bump to 11.0.0 rc 0, regen docs
bump version and regen docs
CHEF-3156 - Be more optimistic about net-ssh
CHEF-2960 - Increase JSON constraint
Add Chef::User class

This commit adds a Chef::User class similar to the Chef::ApiClient
class.  Notable differences are the presence of a password attribute
and the fact that the API will not return chef_type or json_type
attributes.  The latter means that the Chef::REST class will not
automatically inflate API responses to Chef::User objects.
Add user commands to knife.

This commit adds the following commands to knife:

    knife user list
    knife user show USERNAME
    knife user create USERNAME
    knife user delete USERNAME
    knife user reregister USERNAME

Note that since Chef::User objects do not contain a json_class, the
edit object method will not work as expecated.
Update knife-configure to create user rather than client.

Chef 11 now has users as a first-class, authenticatable actors.

    knife configure -i

now creates a user rather than a client.
Chef::User.list should handle responses from Hosted/Private Chef

The API responses from a GET to the "users" endpoint currently returns
a different response on Hosted and Private Chef.  Chef::User.list
transforms this response into form returned by the open source server.