metal binary complains about private key about chef-provisioning

[jkeiser]

The client doesn't ignore the key if you specify it--do you have a ~/.chef/knife.rb, or a .chef/knife.rb in the repository you are presently working in?

[mwrock]

the key is specified in .chef/knife.rb in my repo. I'd like to keep it there for other purposes. However I routinely use chef-zero via chef-client -z and never have this issue.

[jkeiser]

Yeah, it certainly shouldn't be happening--I'm not sure at the moment what could be causing it. I iwould have expected the file to get loaded just like normal in the metal executable.

[jkeiser]

(chef-client -z is likely loading the .pem as well.)

[randomcamel]

@mwrock Both chef-provisioning and chef-client have come a long way: is this still an issue?

[mwrock]

Wow yeah. It has been a while. Just looked at this again and it looks like metal is no longer included in the gemspec's executables as of 37ec6ea so its no longer available at the commandline. I'm gonna close this since it appears this has been abandoned.