chef-api should not require chef

Question

Closed this issue 10 years ago · 3 comments

The stated goal of chef-api is to have as few dependencies as possible. There is an implicit dependency on the chef gem.

`rescue in block in deep_const_get': can't get const Chef::Environment: uninitialized constant Chef (ArgumentError)

This can be avoided by passing create_additions: false into JSON.parse.

PR forthcoming.

Answer 1 · 2014-03-17T20:35:33.000Z

Sorry. What do you mean by "implicit dependency"? Are you saying that Ruby is inflating that class? I thought that was fixed in modern Rubies...

Answer 2 · 2014-03-17T21:27:07.000Z

Yes, this is restricted to systems with 1.9.3.

Answer 3 · 2014-03-17T21:31:05.000Z

Ah makes sense. I don't use 1.9.3 😄