[chef] Re: Re: Re: Re: Cannot find a resource for hostsfile_entry on ubuntu

[Cyril Scetbon < >]

Yes it helps

Thank you guys !

Cyril Scetbon

Le 17 janv. 2014 à 21:56, Daniel DeLeo < "> > a écrit :

On Friday, January 17, 2014 at 12:06 PM, Cyril Scetbon wrote:

On 17 Jan 2014, at 20:21, Daniel DeLeo < "> > wrote:

What `hostsfile` cookbook are you using? Is it this one? https://github.com/customink-webops/hostsfile http://community.opscode.com/cookbooks/hostsfile

Looking at the code on github, this file should be providing the hostsfile_entry resource: https://github.com/customink-webops/hostsfile/blob/master/resources/entry.rb Note that the name of the resource is inferred from the cookbook name plus an underscore plus the file name so you won’t necessarily see the string “hostsfile_entry” in the source.

ok you're right this file is included and contains functions. I've finally made it work with a new fresh repository. where can I find more information about this naming conventions and how it works ? is it related to ruby (I'm not yet an experimented ruby coder) ?

Generally this stuff should be on the docs site, e.g., http://docs.opscode.com/lwrp_custom_resource.html In this case that page doesn’t describe the naming conventions for LWRP resources, so I’ll get in touch with our technical writer about this.

The naming conventions in Chef are generally defined by Chef’s code and not general ruby things. For example, a Chef resource can have any name that is a valid ruby method name and correctly converts to the proper ruby class name (this is based on how Chef converts snake_case_method_names into CamelCaseClassNames). That said, the LWRP DSL removes all of the boilerplate of class definitions so there’s no place for a user to specify what name they want the resource to have, which means that Chef picks the name based on its own conventions.

HTH,

-- 

Daniel DeLeo