Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 0.10.0
-
Component/s: None
-
Labels:None
Description
As a systems engineer I would like the ability to prevent a chef user from uploading a cookbook that already has the same version uploaded before. For example let's say I upload cookbook openssh with version 0.1.0 and three days later I make changes to that cookbook but do not update the version, then when I try to upload it should return 409 CONFLICT or something to that effect. This will ensure that if a role references a versioned cookbook it will not all of a sudden stop working because of a bad update to a cookbook.
I'm going to have a go at this, the freezing will be opt-in on a per-cookbook basis.