| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Signed-off-by: antima-gupta <agupta@msystechnologies.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
Avoid requiring things that are already defined. Rubygems is very slow at traversing the filesystem.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
|
| |
require is quite slow in Ruby and doing requires for things you've already required is also slow. We've used this simple hack in Chef to speed up our requires. In the omnibus installs we patch how rubygems works to make this somewhat pointless, but this will help non-omnibus installs
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
|
|
|
| |
we need strict compliance to rfc2396 or else pedant fails, so this is a
bit less straightforward than most of the other suggestions on how
to fix this problem.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
|
| |
require_relative is significantly faster and should be used when available.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Apply Chefstyle
|
| |
| |
| |
| |
| |
| | |
Autocorrect with the latest chefstyle
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Signed-off-by: Tensibai <tensibai@iabis.net>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
|
| |
Rubocop made it worse
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
| |
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|
|
|
| |
Signed-off-by: Adam Shannon <adamkshannon@gmail.com>
|
| |
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
|
|
|
|
|
|
| |
The ACLs for `cookbook_artifact` objects currently do not include the
creator of the object. Adding the `:create` option to the `set_data`
call (which forwards it on to the `set` method on the data store),
allows the `cookbook_artifact` object to have the creator added to its
ACL.
Signed-off-by: Nolan Davidson <ndavidson@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
| |
because it makes sense for chef-zero
i need it for integration testing against berks to kill off the
uses of the berkshelf-api gem.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
As of POOL-608, the query will return users with the mail `me@mine.com`,
too. While this is technically a little incorrect (only the host part is
case insensitive), most mail providers treat the user part as case
insensitive as well.
Note that this implies that the response may involve more than one user.
But chef-zero behaves like chef-server does, returning them all.
Signed-off-by: Stephan Renatus <srenatus@chef.io>
|
|
|
|
|
| |
* implement rfc090 for named nodes endpoint
Signed-off-by: Jeremy J. Miller <jm@chef.io>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
|
|
|
|
| |
This implements RFC 67, Cookbook Segment Deprecation, for the default
backend of Chef Zero. It also does a little bit of work to make API
versions more ergonomic.
Signed-off-by: Thom May <thom@may.lt>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
| |
Due to a bug in oc-chef-pedant[1], we'd never noticed that this doesn't
return what it should return to match chef-server.
[1]: https://github.com/chef/chef-server/pull/1145
Signed-off-by: Stephan Renatus <srenatus@chef.io>
|