- From: Bryan McLellan <
>
- To:
- Subject: [chef] Re: Re: Re: chef-client auto-registered run_list
- Date: Fri, 23 Dec 2011 13:56:00 -0500
On Fri, Dec 23, 2011 at 6:37 AM, Roberto C. Morano
<
>
wrote:
>
It could be a good idea, but I'm looking for a way to do it from the server.
>
I mean, that way I would have to modify my nodes' chef-client config every
>
time I'd like to add something new to the "default run list" instead of just
>
having it automatically replicated on every new node. This seems pretty
>
unmaintenable for me.
I would put the run_list in a role, and put all the nodes in that role
when they're created.
Then you can centrally manage the role.
>
I'm thinking about running "chef-client -j" to add a default run list with
>
only one recipe that retrieve the real "default run list" from, for example,
>
a databag in the server.
>
It still sounds hacky to me, but at least I wouldn't have to modify my
>
nodes' chef-client config every time manually, just once.
You could probably manage that json file as a cookbook_file or databag
driven template. The next client run should pick it up. Ergh.
Bryan
Archive powered by MHonArc 2.6.16.