| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
| |
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: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
support ! in searches
|
| |
| |
| |
| | |
Signed-off-by: Thom May <thom@may.lt>
|
| |
| |
| |
| | |
Signed-off-by: Scott Christopherson <scott@chef.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This builds on fixes added in #247 and additional tests added in
chef/chef-server#1028.
Handle the query parameters in the search method instead of the get
method to make them more consistent and work properly when start values
are given.
Signed-off-by: Nathan L Smith <smith@chef.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Chef Zero would, on a search request using the "start" or "rows"
parameters, always return all rows.
This change makes it so only the correct number of rows are returned or
the results start at the correct index.
This change will make the tests added in oc-chef-pedant in
chef/chef-server#1028 pass.
Also update the Gemfile to use HTTPS URLs for Git sources, remove unused
comments, and use the Chef Gem from RubyGems as the previous comment
suggested.
Signed-off-by: Nathan L Smith <smith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
|
| |
| |
| |
| |
| |
| | |
FFI_Yajl has never implemented this flag
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
This reverts commit c674dfeacf773579a2eb56cb3c02428268452b50.
|
| |
| |
| |
| |
| |
| | |
FFI_Yajl has never implemented this flag
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Chef Server has the ability to return users and clients separately
within an GET ACL request when `detail=granular`. To support that,
we need to store them separately and determine if we want to present
`actors` or `users` and `clients` at the time of the request.
This change makes a reasonable best effort at capturing the creator
type (user v client) correctly and uses that for determining its
assignment in acls.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Thom May <thom@chef.io>
|
|/
|
|
| |
Signed-off-by: Thom May <thom@may.lt>
|
|
|
|
| |
Signed-off-by: Thom May <thom@may.lt>
|
|
|
|
| |
Signed-off-by: Thom May <thom@may.lt>
|
|
|
|
|
|
| |
Fixes #161
Signed-off-by: Thom May <thom@may.lt>
|
|\
| |
| | |
Return HTTP 400 Bad Request on Solr parse error
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, chef-zero would return an HTTP 500 Internal Server Error
when the Solr parser failed. Now, we return HTTP 400 with an error
message identical to that of the Erchef server. Returning HTTP 400
also improves the end-user experience since knife returns more
sensible error messages.
Before this patch:
> knife search nodes 'recipes:bar::bar'
ERROR: Server returned error 500 for http://127.0.0.1:8889/search...
After:
> knife search nodes 'recipes:bar::bar'
ERROR: knife search failed: invalid search query: 'recipes:bar::bar'
|
|\ \
| | |
| | | |
Set log level to debug in the rescue block.
|
| |/ |
|
|\ \
| | |
| | | |
support URI specific character in file name
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix attempted fall-through in case statement.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
add patch to support chef_version
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
most of our metadata is the form of:
key "value"
but chef_version can be:
chef_version ">= 12.3.1", "< 13.0.0"
so we need a splat in method messing and need to shovel it into an
array.
relates to chef/chef#4081
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix scary search behavior on terms containing dash character
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
add normal tags with empty array
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Increase WEBrick request timeout to 300 seconds. Fixes #137
|