[chef] Re: Re: Why an environment's override_attributes are not set until chef-client completes successfully?

[Adam Jacob < >]

On 2/4/13 10:47 AM, "Jay Pipes" 
<
 >
 wrote:
>>(ie: if chef didn't succeed, how do you know the system is correct, and
>> that you should rely on it?)
>
>This is a silly statement. The purpose of an environment override
>attribute is to describe the intended state of a system belonging to
>that environment. Why on Earth would chef-client succeeding or not
>succeeding change anything related to the intended state of a system
>belonging to an environment?
>
>It just doesn't make sense.

Contrast this with another feature of Chef, which says that a system is
correct when Chef has completed a run successfully. You can absolutely
control when node attributes appear as part of a Chef run - you do it
through calling node.save. By default, though, we assume that the entire
run list was required in order for you to feel comfortable relying on how
the machine behaves. I get that it does not match your use case, and that
it causes you frustration, at least somewhat from being surprised at the
behavior. I'm sorry for that, as we certainly didn't sit down and write
Chef with the explicit purpose of causing you pain.

I, the rest of Opscode, and everyone else on the list (I hope) want
nothing more than for you to be happy and successful - not just with Chef,
but with the entire scope of what you need to be happy in your job. I'm
sorry if my response was too short, and didn't do a good enough job of
conveying that.

Let me know how I can help,
Adam