- From: Miquel Torres <
>
- To:
- Subject: [chef] About Opscode's cookbook repo changes
- Date: Fri, 17 Jun 2011 11:10:45 +0200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=eGPmXHUuk3/bULdiaKH3Kw7jLSDcGq852p697ZcpgI0+l4FSeNV8KVd3rF9StMhAgG PiAsNpEuXYd/xsbFbG8ss5a460wCIJ38RpGZY8gzZbWObBz/t8PQwlRlLCHGmEqpMyWY ssKnh9W0a4eQCSUno6eejkNGjL4jPD73iAaw4=
Hi all,
last month there was a post regarding changes in the opscode cookbooks repo:
http://www.opscode.com/blog/2011/05/24/update-on-the-future-of-opscodes-cookbooks/
While I can understand the reasons that made Opscode remove the
metadata.json from all cookbooks, it does pose a big problem for
non-ruby tools like LittleChef, which depended on JSON to
inter-operate.
Is there a way to generate metadata.json for all cookbooks that
doesn't need a Chef Server?
"knife cookbook metadata" doesn't classify there, unfortunately.
Cheers,
Miquel
- [chef] About Opscode's cookbook repo changes, Miquel Torres, 06/17/2011
Archive powered by MHonArc 2.6.16.