[chef-dev] Re: Open source Chef Server API: big changes in internal code is coming ?

[Noah Kantrowitz < >]

On May 11, 2012, at 6:42 AM, 
<
 >
 wrote:

> Hello,
> 
> We were planning to :
> - modify the base source code of the Open Source Chef REST API
> - use the internal source code of the Open Source Chef REST API in a Rack
> middleware
> 
> But then, we have read that Opscode plan to do big changes in the code 
> bases of
> Chef Server (see below the references), for exemple, switching from Ruby to
> Erlang.
> 
> So we are afraid that we will have to redo our work based on the actual chef
> source code in some months.
> 
> Could you please give more information about the plan changes in code base ?
> for example:
> will the "chef-server-api\app\controllers" source code be totaly changed ?
> if we write ruby code based on open source code of Chef, until when will it 
> be
> usable ?
> 
> We are now thinking that we should only program based on REST API through 
> HTTP
> ( initially we wanted to bypass the HTTP and authentication layer).

The backend implementation will be entirely changed (somewhat unavoidable 
given that it is moving to a new language), but at least at first there will 
be no backwards incompatible changes to the API protocol/format itself. If 
you want something that is going to work more permanently, them yes it would 
be best to grab one of the API client libraries (Spice, PyChef, jclouds-chef, 
etc) and interact with the server through that.

--Noah

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail