delta/ruby-gems/chef.git/lib/chef/knife/raw.rb, branch https_shell

Typos and improved wording

2016-03-06T05:21:39+00:00

When we talk about something requiring a specific version of Chef it helps to specify client vs. server.
If we run key delete the thing we're doing it deleting not destroying

Single space after periods

2016-03-06T05:21:39+00:00

Double spacing is for typewriters. Knife doesn't run on typewriters
http://www.writersdigest.com/online-editor/how-many-spaces-after-a-period

autofixing whitespace cops

2016-02-05T23:00:00+00:00

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

Use double quotes by default

2016-01-14T14:08:03+00:00

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.

Convert all uses of Chef::REST to Chef::ServerAPI

2016-01-11T15:40:42+00:00

In the process, stop auto-expanding JSON in the HTTP client, and let
individual classes control that themselves.

Fixes #2737, Fixes #3518

Add --proxy-auth option to `knife raw`

2015-01-25T21:27:02+00:00

Chef Server 12 and Enterprise Chef Server allow requests made on
behalf of other users by setting the x-ops-request-source HTTP header
to web and signing the request with a particular key (often known as
the "webui key").

This scheme allows the management console to make requests to the API
on behalf of the logged in user.  However, it is also useful for
administrators attempting to debug their Chef Servers or helping their
users in large Chef Server installations.

For example, using the webui_key and this option, an adminstrator can
list nodes in different orgs, without access to a particular user's
key.

    > knife raw /organizations/wonderbolts/nodes -k webui_priv.pem \
      -u soarin -s https://api.opscode.piab --proxy-auth

    {

    }

    > knife raw /organizations/acme/nodes -k webui_priv.pem
      -u wei -s https://api.opscode.piab --proxy-auth

    {

    }

The webui key exists on the Chef Server itself and is only accessible
to an administrator with root access.  As such, this is typically an
advanced debugging tool and isn't likely needed in other knife
subcommands.

- Adding X-Remote-Request-Id to the set of headers for every request from CCR and

2014-02-07T23:31:10+00:00

knife that will be sent to erchef
- Each knife request has a different X-Remote-Request-Id, where as it
remains the same for all requests originating from the same chef-client
run.
- Adding and fixing tests

Remove :raw_input option to JSONInput, use Chef::HTTP for knife raw

2013-10-09T20:53:37+00:00

CHEF-4515: upload sometimes inflates JSON. Fix by using true raw version of Chef::REST

2013-10-09T16:21:02+00:00

Make knife raw --pretty work

2013-09-13T06:10:54+00:00