delta/ruby-gems/chef.git - github.com: opscode/chef.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update to RSpec 3.	Claire McQuin	2014-10-29	1	-50/+50
\|
*	My local gemset was including the `json` gem, causing these tests to be ↵	tyler-ball	2014-10-07	1	-1/+1
\| \| \| \|	ineffective. Also made them more clear
*	Trying to eradicate all traces of the JSON gem from Chef	tyler-ball	2014-10-07	1	-1/+5
\|
*	[CHEF-5328] Added tests for Chef::User.list with inflate=true	Xabier de Zuazo	2014-05-24	1	-0/+12
\|
*	s/mock\(/double(/g	Lamont Granquist	2014-01-29	1	-1/+1
\|
*	s/stub!/stub/g	Lamont Granquist	2014-01-29	1	-3/+3
\| \| \| \|	fix deprecation warnings
*	User tests are about users, avoid '@client' as a variable name.	Steven Danna	2013-02-06	1	-27/+27
\|
*	Use same name validations as used by the server in user model.	Steven Danna	2013-02-06	1	-0/+14
\|
*	Chef::User.list should handle responses from Hosted/Private Chef	Steven Danna	2013-02-06	1	-0/+20
\| \| \| \| \| \|	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.
*	Add Chef::User class	Steven Danna	2013-02-06	1	-0/+221
	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.