This repository was archived by the owner on Jul 14, 2021. It is now read-only.
Add a command that can debug why a cookbook gets a given identifier #1682
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.
Signed-off-by: Daniel DeLeo dan@chef.io
Description
Adds a command that dumps the identifier data so users can figure out why a given cookbook has a given identifier. It often happens that somewhere in a Ci pipeline or between two developers laptops there is some mysterious difference between cookbooks that makes the identifier "flap." This should make it easier to understand what's going on.
Issues Resolved
I can't find the links but this comes up every so often in discourse and slack.
Check List