[chef] Re: Best practice to declare an attribute that must be defined outside the cookbook?

[DV < >]

That's exactly what I see most cookbooks doing - setting default attributes to nil when they aren't supposed to be set to anything by default.

On Mon, Jun 9, 2014 at 6:35 AM, Stephen Corbesero < " target="_blank"> > wrote:

What is the best way to declare an attribute in attributes/default.rb which is really expected to be defined at a higher level, say an environment or even a wrapper cookbook?  I am reluctant to give it a default value, since  it is too easy to forget to change it when a cookbook gets deployed.  In the past we have used entries like “invalid” if it is a string, or an illegal number based on the context.

 

Should I just go all the way and use ‘nil’?  As well as adding an explicit check in the recipe to look for the undefined value and log a descriptive message?

 

 

 

--

Stephen Corbesero, DevOps Engineer

Synchronoss - Mobile Innovation for a Connected World

Office: +1 484-821-4272

" target="_blank"> | www.synchronoss.com

 

--
Best regards, Dmitriy V.