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


Chronological Thread 
  • From: Adam Jacob < >
  • To: " " < >
  • Subject: [chef] Re: Re: Re: Why an environment's override_attributes are not set until chef-client completes successfully?
  • Date: Mon, 4 Feb 2013 18:41:23 +0000
  • Accept-language: en-US

On 2/4/13 9:27 AM, "Jay Pipes" 
< >
 wrote:
>Yes, we ended up having to use node.save in a Galera cluster cookbook
>were were using when we saw that Chef searches were entirely
>non-deterministic if you were relying on attributes that would only be
>set if the chef-client run had succeeeded. It's a major design flaw, IMHO.

One man's design flaw is another mans safety feature. :)

(ie: if chef didn't succeed, how do you know the system is correct, and
that you should rely on it?)

Love,
Adam





Archive powered by MHonArc 2.6.16.

§