metal command seems to not use .chef/knife.rb.

[rberger]

The metal cli command doesn't seem to use the configuration info in .chef/knife.rb. Seems to always use chef-zero even if I pass in the chef server url with -S. And it doesn't seem to pick up any other parameters from .chef/knife.rb

[hntd187]

@rberger I've been loading my knife config manually into recipes to get around this, it seems to spin up a chef zero server whether you want it or not, which is definitely a bug if you provide a chef server details to metal.

[jkeiser]

The command line definitely needs some work (I removed it from the readme
due to this and plan to add it back in 0.12). I'm a little surprised it
takes nothing from .chef/knife.rb, though.

On Mon, Jun 9, 2014 at 7:30 AM, hntd187 [email protected] wrote:

@rberger https://github.com/rberger I've been loading my knife config
manually into recipes to get around this, it seems to spin up a chef zero
server whether you want it or not, which is definitely a bug if you provide
a chef server details to metal.

—
Reply to this email directly or view it on GitHub
#70 (comment).

[randomcamel]

@rberger There have been quite a lot of changes in all the relevant repos since this was filed: is it still an issue?

[rberger]

Heh, not sure. I've been explicitly specifying .chef/knife.rb on the chef-provisioning command line. If John thinks its fixed, its probably fixed.

[tyler-ball]

I'm going to close this since we don't support the metal CLI anymore, and running chef-client has been picking up my local .chef/knife.rb file recently