summaryrefslogtreecommitdiff
path: root/spec/unit/user_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* autofixing whitespace copsLamont Granquist2016-02-051-10/+9
| | | | | | | | | | | | | | | | | | | | | | 4174 Style/SpaceInsideHashLiteralBraces 1860 Style/SpaceAroundOperators 1336 Style/SpaceInsideBlockBraces 1292 Style/AlignHash 997 Style/SpaceAfterComma 860 Style/SpaceAroundEqualsInParameterDefault 310 Style/EmptyLines 294 Style/IndentationConsistency 267 Style/TrailingWhitespace 238 Style/ExtraSpacing 212 Style/SpaceBeforeBlockBraces 166 Style/MultilineOperationIndentation 144 Style/TrailingBlankLines 120 Style/EmptyLineBetweenDefs 101 Style/IndentationWidth 82 Style/SpaceAroundBlockParameters 40 Style/EmptyLinesAroundMethodBody 29 Style/EmptyLinesAroundAccessModifier 1 Style/RescueEnsureAlignment
* Some more author domain stragglers.Noah Kantrowitz2016-02-021-1/+1
|
* Replace all Opscode copyrights with Chef Software.Noah Kantrowitz2016-02-021-1/+1
| | | Created via git ls-files | xargs perl -pi -e "s/(Copyright.*?), Opscode(,)? Inc(\.)?/\\1, Chef Software Inc./gi"
* Copyright year update for 2016 and massive cleanup.Noah Kantrowitz2016-02-021-1/+1
| | | Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"
* Use double quotes by defaultThom May2016-01-141-3/+3
| | | | | | | This is an entirely mechanically generated (chefstyle -a) change, to go along with chef/chefstyle#5 . We should pick something and use it consistently, and my opinion is that double quotes are the appropriate thing.
* Remove _rest from http methods.tylercloke2015-07-061-8/+8
|
* Move Chef::OscUser back to Chef::User namespace and new user code to ↵tylercloke2015-07-061-408/+100
| | | | | | Chef::UserV1. Also, have Chef::User (formally Chef::OscUser) use API V0 to make requests.
* Only automatically set resources that do class X < Chef::Resource,jk/3524John Keiser2015-06-161-1/+1
| | | | not X = Class.new(Chef::Resource)
* Better API version error handling helper code.tylercloke2015-06-051-4/+4
| | | | Renamed Chef::Mixin::ApiVersionRequestHandling.handle_version_http_exception -> server_client_api_version_intersection and made it do much more useful / sane things. See comments for details.
* Reregister V0 support for Chef::Client.tylercloke2015-06-051-0/+29
|
* Fixed bug where boolean fields would not be populated in Chef::User/ApiClient.tylercloke2015-06-051-3/+8
|
* API V1 support for client creation.tylercloke2015-06-051-98/+32
|
* Small updates to Chef::User.list.tylercloke2015-06-051-10/+0
|
* Added V1 support to Chef::User.update and removed admin field.tylercloke2015-06-051-47/+145
|
* Added versioned Chef Object API support code and repaired Chef::User.create.tylercloke2015-06-051-77/+334
| | | | Also added Chef::User.create V1 API support. Chef::User.create will attempt to use V1 of the server API, and if it fails, it will fall back to V0.
* Update to RSpec 3.Claire McQuin2014-10-291-50/+50
|
* My local gemset was including the `json` gem, causing these tests to be ↵tyler-ball2014-10-071-1/+1
| | | | ineffective. Also made them more clear
* Trying to eradicate all traces of the JSON gem from Cheftyler-ball2014-10-071-1/+5
|
* [CHEF-5328] Added tests for Chef::User.list with inflate=trueXabier de Zuazo2014-05-241-0/+12
|
* s/mock\(/double(/gLamont Granquist2014-01-291-1/+1
|
* s/stub!/stub/gLamont Granquist2014-01-291-3/+3
| | | | fix deprecation warnings
* User tests are about users, avoid '@client' as a variable name.Steven Danna2013-02-061-27/+27
|
* Use same name validations as used by the server in user model.Steven Danna2013-02-061-0/+14
|
* Chef::User.list should handle responses from Hosted/Private ChefSteven Danna2013-02-061-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 classSteven Danna2013-02-061-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.