As per subject. Could anyone explain a bit about the new features in chef
0.8?
Thanks
Dikang
On Thu, Dec 10, 2009 at 4:53 PM, Dikang Gu dikang85@gmail.com wrote:
As per subject. Could anyone explain a bit about the new features in chef
0.8?
I know you got this answer in IRC, but I wanted to drop a quick
message to the list for others who may be curious:
- New API authentication mechanism based on signed headers, giving us
a ton of benefits (replay attack protection, stateless, etc.) - OpenID still works in the Web UI, but only for users
- Web UI now talks exclusively to the API
- Knife, a command line interface to the REST API, now has 100%
coverage of the API from the CLI, with $EDITOR support. - Search indexing has been re-worked to be fast and stable
- The API for the internal Chef objects (nodes, roles, etc.) look like
normal ruby CRUD objects - Data Bags have been added to the system - you can now easily store
arbitrary JSON, have it be indexed, and easily used in recipes. (Think
a bunch of User objects, for example.) - Shef, a Chef REPL, has been added by Dan DeLeo. It also includes
the ability set breakpoints in the Chef run, so you can do totally
sweet interactive debugging of Chef runs!
That's a few of the big things, but there are a bunch more. 
Adam
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
Thank you Adam!
Dikang
On Sat, Dec 12, 2009 at 3:22 AM, Adam Jacob adam@opscode.com wrote:
On Thu, Dec 10, 2009 at 4:53 PM, Dikang Gu dikang85@gmail.com wrote:
As per subject. Could anyone explain a bit about the new features in chef
0.8?I know you got this answer in IRC, but I wanted to drop a quick
message to the list for others who may be curious:
- New API authentication mechanism based on signed headers, giving us
a ton of benefits (replay attack protection, stateless, etc.)- OpenID still works in the Web UI, but only for users
- Web UI now talks exclusively to the API
- Knife, a command line interface to the REST API, now has 100%
coverage of the API from the CLI, with $EDITOR support.- Search indexing has been re-worked to be fast and stable
- The API for the internal Chef objects (nodes, roles, etc.) look like
normal ruby CRUD objects- Data Bags have been added to the system - you can now easily store
arbitrary JSON, have it be indexed, and easily used in recipes. (Think
a bunch of User objects, for example.)- Shef, a Chef REPL, has been added by Dan DeLeo. It also includes
the ability set breakpoints in the Chef run, so you can do totally
sweet interactive debugging of Chef runs!That's a few of the big things, but there are a bunch more.
Adam
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com