[chef-dev] Re: generating node configuration files with knife -- plugin or patch chef/ core?

[Bryan Berry < >]

> I am curious what your process is here. Do you create a node from this JSON immediately thereafter?

Yes, exactly. Next I bootstrap the node. Ideally I would combine creating in chefserver and bootstrapping the node.

The primary motivation is to give my users the ability to see which recipes/roles. They are also used to everything being under version control so they like the idea of having the node definitions under source control.

While they can't actually see all the recipes applied to a node because of roles, they understand roles so can read through the corresponding role definitions.

> Or should i try to modify chef code itself to add this trivial piece of functionality? I haven't had a lot of luck with my > pull requests lately. I am not sure if it is because my code is crap (highly possible) or if you the chef-devs are >extremely busy (also highly possible)

> Busy, but what stage are your pull requests at? Do they have associated tickets that are marked fixed/resolved?

I haven't written it yet because I haven't had much success with my pull requests as of late. I thought I would gauge how much interest you have before patching chef/ or writing a knife plugin.

lastly, what on earth is a "loftninja"?

On Mon, Nov 28, 2011 at 9:48 PM, Bryan McLellan < "> > wrote:

On Nov 27, 2011 2:30 PM, "Bryan Berry" < " target="_blank"> > wrote:
>
>  I was thinking of writing a knife plugin  so that you could run $ knife node create --to-file foo1  ; it writes a json doc to  chef-repo/nodes/foo1.json  with a basic template

I am curious what your process is here. Do you create a node from this JSON immediately thereafter?

> Or should i try to modify chef code itself to add this trivial piece of functionality? I haven't had a lot of luck with my pull requests lately. I am not sure if it is because my code is crap (highly possible) or if you the chef-devs are extremely busy (also highly possible)

Busy, but what stage are your pull requests at? Do they have associated tickets that are marked fixed/resolved?

We haven't been merging much for 0.10.8 because were trying to get 0.10.6 out the door right now.

Bryan