- From: Lucian Ciufudean <
>
- To:
- Subject: [chef] Re: Re: Re: metadata and cookbook names
- Date: Tue, 15 Oct 2013 14:06:57 +0300
Thanks, I asked this because I'm seeing all kinds of community
content. For example cookbook 'subversion' got a name attribute in
metadata.rb only 11 months ago.
On Fri, Oct 11, 2013 at 11:04 PM, steve .
<
>
wrote:
>
metadata.rb is definitely required.
>
>
In fact, I believe the cookbook name in metadata.rb is actually honored over
>
the directory name...
>
>
>
On Fri, Oct 11, 2013 at 8:08 AM, Andrew Gross
>
<
>
>
wrote:
>
>
>
> 1. Assume metadata.rb is required. I am not 100% sure if Chef can operate
>
> without one in the cookbook, but you should set up a commit hook so that it
>
> forces the metadata.rb file to exist.
>
>
>
> 2. The name is metadata.rb is respected. All dependency resolvers should
>
> unpack the cookbooks and parse the metadata file to find the name.
>
>
>
> For an example check out "cookbook-elasticsearch".
>
>
>
>
>
> https://github.com/elasticsearch/cookbook-elasticsearch/blob/master/metadata.rb
>
>
>
> The name in metadata.rb is "elasticsearch" and that is how it is referred
>
> to internally.
>
>
>
>
>
> On Fri, Oct 11, 2013 at 9:50 AM, Lucian Ciufudean
>
> <
>
>
> wrote:
>
>>
>
>> Hi guys,
>
>>
>
>> A have a couple of questions in this area:
>
>>
>
>> 1. Is the metadata.rb file mandatory in a cookbook?
>
>> 2. if metadata.rb is present, and it specifies a different name than
>
>> the cookbook archive filename, which is the name considered by
>
>> cookbook dependency resolution alg during a chef-run?
>
>>
>
>> Thanks,
>
>> Lucian
>
>
>
>
>
Archive powered by MHonArc 2.6.16.