[chef] Re: metadata and cookbook names

[Andrew Gross < >]

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 < " target="_blank"> > 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