[chef] RE: Cookbook Attributes Best Practices/Guidelines ?

[Curtis Stewart < >]

Here's a good post about arrays and attributes: 
https://coderanger.net/arrays-and-chef/.  Compliments of Noah Kantrowitz.

I try to follow a practice of not creating attributes until necessary.  It's 
easy to overdo it with attributes, and that just complicates matters.  

Also, some of that Chef Style guides out there have good practices for 
attribute naming: 
https://github.com/secondmarket/chef-style-guide#system-and-component-naming. ;

Thanks,
Curtis
--

Curtis Stewart
Consultant

 
6500 River Place Blvd, Bldg. 6, Austin, TX 78730
512.813.3416 Office
512.567.8476 Mobile



-----Original Message-----
From: Benzinger, Dennis 
[mailto:
 
 
Sent: Friday, July 24, 2015 7:02 AM
To: 

 
Subject: [chef] Cookbook Attributes Best Practices/Guidelines ?

Hello List,

what are some good websites or presentations about best practices/guidelines 
for attributes in cookbooks? 

For example about:
- Naming of the attribute files
- Naming of the attributes themselves
- Arrays vs. hashes
- And especially interesting for me:
  
  When to use node.run_state instead of an attribute?

  I've seen cookbooks which put every variable in an attribute even if it is 
used
  only internally. Wouldn't it be better to use node.run_state in this case? 
At
  least as long as you don't have to store it between Chef runs.


Thanks,
Dennis Benzinger | hybris

--
Dennis Benzinger
IT Architecture Senior Specialist
hybris Cloud Services

 

hybris GmbH
Nymphenburger Straße 86
80636 München, Germany
Fax +49 89 890 65 555
www.hybris.com
hybris GmbH, Nymphenburger Str. 86, 80636 München, Deutschland. 
Geschäftsführer: Ariel F. Lüdi, Carsten Thoma, Michael Zips. 
Amtsgericht München, HRB 124384.