| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
should fully convert to using ffi-yajl
there are still issues with JSON gem monkeypatching interacting with
chef-zero and the spec tests so we keep the requires here for the
json gem and the ffi_yajl/json_gem here. when ohai and chef-zero are
fixed, we an just require ffi_yajl.
|
| |
|
|
| |
This reverts commit adbb0fa85cc45b93ba91dc3019094b312cafb35c.
|
| | |
|
| |
|
|
|
| |
This means the validator/public_key/admin fields of the ApiClient
object now get set properly
|
| |
|
|
| |
This makes it possible to create new validator clients using knife.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
After discussing with Adam and Seth F, there's no reason not to put the
private key in the serialized representation if we have it.
We ought to carefully review for behavior changes on the server side
before backporting to 10.x
|
| | |
|
| |
|
|
|
|
|
|
| |
Without this change it's not possible to fix CHEF-3662 on the client
without modifying Chef::REST to ignore json_class. Previously the
behavior was explicitly defined to be the opposite, but the reasoning
behind this decision wasn't documented; I suspect it may have been for
server-side behavior that's no longer necessary.
|
| | |
|
|
|
The opscode/chef repository now only contains the core Chef library code
used by chef-client, knife and chef-solo!
|
