Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Better "not a cookbook" errors #566

Merged
merged 2 commits into from
Oct 19, 2015
Merged

Better "not a cookbook" errors #566

merged 2 commits into from
Oct 19, 2015

Conversation

danielsdeleo
Copy link
Contributor

Fixes #564 and a similar bug I discovered in testing.

Error messages now look like:

Building policy example-application-service
Expanded run list: recipe[apt::default]
Caching Cookbooks...
Installing foo >= 0.0.0 from path
Error: Failed to generate Policyfile.lock
Reason: (CookbookOmnifetch::NotACookbook) The resource at '/Users/ddeleo/oc/chef-dk/no/such/dir/foo' does not appear to be a valid cookbook. Does it have a metadata.rb?

@danielsdeleo
Require CookbookOmnifetch 0.2.2+, improves error messages
08d516d 
See: chef/cookbook-omnifetch#2
@danielsdeleo
Give CookbookLocationSpecification a usable string representation
439d09a 
These show up in some errors generated inside CookbookOmnifetch (in
particular if you have code like `cookbook "foo", ">= 5.0", path: "foo"`
in your Policyfile.rb, but the cookbook there doesn't satisfy the
version constraint).
@danielsdeleo danielsdeleo merged commit 439d09a into master Oct 19, 2015
@danielsdeleo danielsdeleo deleted the better-not-a-cookbook-errors branch October 19, 2015 18:42
ksubrama pushed a commit that referenced this pull request Jan 11, 2016
@btm
Merge pull request #566 from chef/btm/fix-postinst
65a4c9c 
solaris sh compatible verify-chef.sh
@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@danielsdeleo @chef-supermarket