[chef-dev] Re: Re: Dialect support and loading enhancements


Chronological Thread 
  • From: Noah Kantrowitz < >
  • To: Chef Dev < >
  • Subject: [chef-dev] Re: Re: Dialect support and loading enhancements
  • Date: Fri, 20 Sep 2013 09:08:47 -0700

Can you be more specific? Is the worry that people will demand training in 3rd party tools? Or that people will already know a non-ruby thing and it will be harder to get them going on the opscode training materials since the might have to "unlearn" some stuff. If the latter, I think the same argment of knowledge mapping applies. It means care must be taken is designing new dialects, but that's a thing we can do.

--Noah

mandi walls < > wrote:
Ha! I second that emotion. 

On Friday, September 20, 2013, Sean OMeara wrote:
As someone who regularly has to train people in Chef, dialects scares the living crap out of me.

-s


On Thu, Sep 19, 2013 at 1:37 PM, Noah Kantrowitz < ');" target="_blank"> > wrote:
https://github.com/opscode/chef/pull/997

At long last I've pushed up a completed-enough-to-use version of my [dialects proposal](https://gist.github.com/coderanger/a6e0c627d349f0712dcc). I won't repeat the whole document here, but some highlights:

1. Hooks to load Chef recipes and attribute files from formats other than .rb
2. JSON and Yaml dialects for attribute files.
3. Root shortcuts for cookbook source files of which you commonly have only one.
    cookbooks/
      apache2/
        attributes.rb
        recipe.rb
        library.rb
4. Removal of the need for the default/ path segment under files/ and templates/.
5. Ability to pass an array to #source on cookbook_file and template to define your own lookup path similar to the current implicit one.

Personally I think all of these put together are an order of magnitude improvement in ease of learning Chef and writing new cookbooks while not losing any of the expressive power you want on the high end. This branch should present no backwards incompatibilities, though I think it should kick off a discussion separately about deprecating the implicit search path on files/ and templates/ in favor of people using the new explicit search path syntax for the rare occasions where such things are desired (and even in those cases, it is generally just a few of the options in the current search path). Any such deprecation would have to be over a very long time though. I have opened https://tickets.opscode.com/browse/CHEF-4559 to track this patch. If anyone has any feedback please don't hesitate to shoot me an email or comment on the pull request/ticket.

--Noah






Archive powered by MHonArc 2.6.16.

§