Use Knife's builtin facility to configure chef.

[meineerde]

This allows to place the knife.rb in any of the supported locations, e.g. inside a chef repo.

[chrisa]

Hi,

Thanks for this - it definitely makes sense to follow knife's behaviour here.

It looks like this doesn't set the knife verbosity level though, which forces the Chef log level to :debug -- is there a way to default that so that the log level is taken from knife.rb?

You can see this running the tests:

➔  bundle exec rake 
/Users/chris/.rvm/rubies/ruby-1.9.2-p320/bin/ruby -S rspec ./spec/client_spec.rb ./spec/command_spec.rb ./spec/issued_certificate_spec.rb ./spec/request_spec.rb ./spec/signing_authority_spec.rb
..DEBUG: Using configuration from /Users/chris/Projects/venda/chef/upstream-cookbooks/ssl/client-gem/spec/fixtures/chef/knife.rb
.DEBUG: Using configuration from /Users/chris/Projects/venda/chef/upstream-cookbooks/ssl/client-gem/spec/fixtures/chef/knife.rb
.DEBUG: Using configuration from /Users/chris/Projects/venda/chef/upstream-cookbooks/ssl/client-gem/spec/fixtures/chef/knife.rb
.DEBUG: Using configuration from /Users/chris/Projects/venda/chef/upstream-cookbooks/ssl/client-gem/spec/fixtures/chef/knife.rb
....................

Finished in 1.25 seconds
25 examples, 0 failures
Coverage report generated for RSpec to /Users/chris/Projects/venda/chef/upstream-cookbooks/ssl/client-gem/coverage. 192 / 297 LOC (64.65%) covered.

[meineerde]

Turns out that after CHEF-2150 knife doesn't really use the chef logger anymore. Instead, in knife the log level is set on the command line by passing -V which sets the verbosity.

We have to be a bit ugly to work around the stages on which the verbosity setting is translated to an actual log_level. But given that knife is intended to be run on :error anyways with apparently no way to change that ion knife.rb, I figured it would be okay to set it fixed to :error.

[chrisa]

Thanks, that's great. Merged in version 1.0.3.