search

X0nic / chef-bginfo

1 stars 0 forks source link

Metadata requires 'name' attribute #1

Open tsgood77 opened 8 years ago

tsgood77 commented 8 years ago

At some point, Chef Server started requiring a name entry in the metadata. Without it, community users cannot wrapper your cookbook without modifying it which is not a good pattern to follow.

$ knife cookbook upload notepadplusplus -o ~/Development/cookbooks ERROR: Chef::Exceptions::MetadataNotValid: Cookbook loaded at path(s) [/Users/timgood01/Development/cookbooks/notepadplusplus] has invalid metadata: The `name' attribute is required in cookbook metadata

X0nic commented 8 years ago

I can add the meta info and push out a new cookbook. What I can't do is test it very easily. Are you up for the challange @tsgood77 ?

tsgood77 commented 8 years ago

Nathan,

I am but....at this point I am not working on the most recent client or chef server. I am on 11.x.x for both of these. Moreover, I have always wanted to move into TestKitchen, ChefDK, etc. but most of my stuff IS windows and every time I look back it does not seem that all of this has been fully/seamlessly implemented for Windows. So my old Berkshelf (2.0.18) and Window VM's run in Vagrant are my test bed.

I do know I ran into this before with a previous cookbook (can't recall which) at the point when the 'name' attribute became required. I requested a fix and it was. (That cookbook may well have been one of yours). Wonder if anyone complained about that one. ;-)

Let me know what you are thinking.

Tim

On Wed, Nov 4, 2015 at 12:25 PM, Nathan Lee notifications@github.com wrote:

I can add the meta info and push out a new cookbook. What I can't do is test it very easily. Are you up for the challange @tsgood77 https://github.com/tsgood77 ?

— Reply to this email directly or view it on GitHub https://github.com/X0nic/chef-bginfo/issues/1#issuecomment-153799407.