Make sure path/scm location is used during dependency resolution #976
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.
This fixes two problems when using path and SCM locations:
Custom cookbook on given location uses different dependencies
For example if someone uses a local/scm cookbook with the same name/version available in the community cookbook site, the dependencies of the community cookbook will be added to the resolution graph. This change stops to populate the dependency graph with any cookbook dependencies from global sources if a local cookbook is already present.
Solve graph only using the demanded location cookbook version
If a location is specified, the cookbook constraint should be locked to that version automatically.
Fixes #975.