Using 2.x.
On Wednesday, June 5, 2013, Brad Knowles wrote:On Jun 5, 2013, at 12:36 PM, Ranjib Dey < > wrote:
> the problem is chef server does not mandate version freeze for cookbooks. You can upload the different content with same version, so for an external tool like berkshelf its impossible to understand if the cookbook has changed (since version is not the absolute indicator) , unless it does a full download checksum based comparison (this is how chef-client works). So its risky for a tool like berkshelf to do this, but definitely its a good option to have (in that case you might also like to specify only a subset of cookbooks for which you want to do this).
OTOH, Berkshelf could be configured to automatically update the version number on every change and freeze the version after uploading. Since the version would have been incremented and frozen by Berkshelf itself, it should be safe to assume that the cookbook is unchanged if the version number hasn't changed.
Yes, I know people could un-freeze and then manually upload a different version with the same version number, but if they want to shoot themselves in the foot like that, then we should be prepared to let them do so.
--
Brad Knowles < >
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
--
--~*~ StormeRider ~*~"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
Archive powered by MHonArc 2.6.16.