- From: "Julian C. Dunn" <
>
- To:
- Subject: [chef] Re: RE: Re: CHEF-3506 - Don't save the node object when using an override run list?
- Date: Tue, 17 Sep 2013 09:04:44 -0400
On Tue, Sep 17, 2013 at 7:13 AM, Kevin Keane Subscription
<
>
wrote:
>
Wouldn't a change to the current behavior break bootstrapping? I believe it
>
relies on being able to override the run_list, where the overridden run_list
>
is responsible for the initial setup of the node.
The current bootstrap procedure writes a run_list to first-boot.json
and then loads it with "chef-client -j" -- not quite the same thing as
"-o".
- Julian
- [chef] CHEF-3506 - Don't save the node object when using an override run list?, Bryan McLellan, 09/16/2013
- [chef] Re: CHEF-3506 - Don't save the node object when using an override run list?, Sam Pointer, 09/17/2013
- [chef] RE: Re: CHEF-3506 - Don't save the node object when using an override run list?, Kevin Keane Subscription, 09/17/2013
- [chef] Re: RE: Re: CHEF-3506 - Don't save the node object when using an override run list?, Julian C. Dunn, 09/17/2013
- [chef] Re: Re: CHEF-3506 - Don't save the node object when using an override run list?, Adam Leff, 09/17/2013
- [chef] Re: Re: CHEF-3506 - Don't save the node object when using an override run list?, Bryan McLellan, 09/17/2013
- [chef] Re: Re: CHEF-3506 - Don't save the node object when using an override run list?, Lamont Granquist, 09/18/2013
- [chef] RE: CHEF-3506 - Don't save the node object when using an override run list?, Kadel-Garcia, Nico, 09/18/2013
- [chef] RE: CHEF-3506 - Don't save the node object when using an override run list?, Chris Sibbitt, 09/27/2013
Archive powered by MHonArc 2.6.16.