[chef] Re: Should name be in the boilerplate fo r metadata.rb… WAS: Re: Re: How to get test-kitchen to work when cookbook is named "cookbook-x"

[Mike < >]

> Should the name attribute be added to the boilerplate metadata.rb?
My vote is "yes".

This especially has usefulness when I may have a cookbook named
"apache2" in my corp repo, and if I fork the
opscode-cookbooks/apache2, I pretty much have to rename the repo to
something sane, like 'opscode-apache2` or something like that.

I can then clone locally and call it whatever I like, like Andrea
mentioned he does, but then again, I may have a conflict.

Tools like librarian and berkshelf should be able to parse the `name`
attribute as well, and place things correctly - I haven't confirmed
any of that.

-M

On Tue, Nov 13, 2012 at 5:47 PM, Jeffrey Hulten 
<
 >
 wrote:
>
> I have run across a couple of cases where this bit me or others. Should the 
> name attribute be added to the boilerplate metadata.rb?
>
> --
> Jeffrey Hulten
> Principal Consultant at Automated Labs, LLC
> 
 
>   206-853-5216
> Skype: jeffhulten
>
> On Nov 13, 2012, at 2:40 PM, Jay Pipes wrote:
>
>> On 11/13/2012 05:36 PM, Mike wrote:
>>> Jay,
>>>
>>> A quick fix might be to declare the "name:" attribute in your
>>> cookbook's metadata.rb.
>>>
>>> it's not a required field, and I've found that being explicit solves a
>>> lot of the foodcritic-related rules on this.
>>
>> Thanks Mike! That indeed got rid of the FC007 errors.
>>
>> I will continue to plod through the test-kitchen tutorials :)
>>
>>
>> Again, thanks!
>> -jay
>