[chef] Re: Re: Re: Re: question about data bags - best practice


Chronological Thread 
  • From: Daniel DeLeo < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: question about data bags - best practice
  • Date: Tue, 6 Aug 2013 08:37:14 -0700


On Tuesday, August 6, 2013 at 8:27 AM, Vladimir Skubriev wrote:

On 06.08.2013 19:01, Daniel DeLeo wrote:
There is a hash on the node object you can use for per-run state info.
It is not persisted to the server. To access it:

node.run_state[:my_key] = "my value"
how can i link run_state attributes to mysql cookbook attributes ?

example:

node.run_state['mysql']['server_root_password'] = item['password']

then it is not persisted to the server ?
`node.run_state` is a separate field in the node object that is not included in the serialized json. You can see for yourself by printing `node.to_json`.
 

Who can access to node attributes on the server? In previous message i
suggested that only node, which run their recipes.
All node attributes are publicly readable by all other nodes via search.
 

Then why i must use node.run_state ?
The run_state field is generally useful for storing any data that you only need to keep for the duration of the chef run.
 

is i am right ?


--
Best regards,

CVision Lab System Administrator
Vladmir Skubriev



-- 
Daniel DeLeo




Archive powered by MHonArc 2.6.16.

§