Relax version constraints for dependencies #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We need to use >= instead of ~> for version constraints because Chef Policies use "dotted decimal identifier" versions that result in integers that will never match the "normal" cookbook versions we use. For example, the version constraint: ~> 3.2 is what we used. However, the dotted decimal version may be 30625036585770760.42672982950081083.162968991950205 The dotted decimal version is used in the "backwards compatibility mode" for Chef Zero as it doesn't have the native Policy document API (yet). This may result in a 412 precondition failed exception when using the pessmistic version constraint.
jtimberman
added a commit
that referenced
this pull request
Oct 13, 2015
Relax version constraints for dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to use >= instead of ~> for version constraints because Chef
Policies use "dotted decimal identifier" versions that result in
integers that will never match the "normal" cookbook versions we use.
For example, the version constraint:
~> 3.2
is what we used. However, the dotted decimal version may be
30625036585770760.42672982950081083.162968991950205
The dotted decimal version is used in the "backwards compatibility
mode" for Chef Zero as it doesn't have the native Policy document API
(yet). This may result in a 412 precondition failed exception when
using the pessmistic version constraint.