[chef] Re: Re: [Chef] Attribute precedence and Persistence issue.

[Mrigesh Priyadarshi < >]

Hey Julian,

our use case is That we have a service portal and we want end users to provision their instance with custom config

Warm Regards,

Mrigesh Priyadarshi

Mob:-+91-720-402-2510
             

On Fri, Nov 22, 2013 at 9:38 PM, Julian C. Dunn < " target="_blank"> > wrote:

On Thu, Nov 21, 2013 at 10:51 PM, Mrigesh Priyadarshi
< "> > wrote:

> I am working on a requirement which states that a particular version of a
> software needs to be installed on a VM and the version could be changed as
> per the user requirement.
>
> I thought to put the default value in attribute and let it be overridden by
> the JSON attrib which can be passed on run time. It works fine but it starts
> cribbing the moment i dont pass the the JSON attrib in next run, in the
> ideal scenario the attribute should fall back to Attribute file to take the
> value.
>
> But in this case it is taking up the value persisted on node which we passed
> in the JSON attrib.

Attributes are always persisted to the node object.

I'm not totally clear on your use case. Chef is for policy compliance.
If software X needs to be installed at version Y on a system, it will
continue ensuring that version Y will be on the system.

- Julian

--
[ Julian C. Dunn < "> >          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]