Skip to content
This repository has been archived by the owner on Sep 19, 2020. It is now read-only.

Cookbook version is specified in metadata #347

Closed
nathenharvey opened this issue Aug 11, 2015 · 2 comments
Closed

Cookbook version is specified in metadata #347

nathenharvey opened this issue Aug 11, 2015 · 2 comments
Milestone

Comments

@nathenharvey
Copy link
Contributor

Every cookbook should include a version in the metadata file. This is not strictly required though. The Chef server will assign version 0.0.0 to a cookbook that is uploaded without a version.

Foodcritic should include a rule to verify that the metadata file includes a version key.

@jjasghar
Copy link

👍 This seems not only obvious, but I know i've always assumed this. We should make a rule to check for this. 👍

the two things in a metadata.rb to make a "valid cookbook" are:

  • name
  • version

Even though when you do a knife cookbook generate the metadata.rb comes out with:

name             'awesome'
maintainer       'The Authors'
maintainer_email '[email protected]'
license          'all_rights'
description      'Installs/Configures awesome'
long_description 'Installs/Configures awesome'
version          '0.1.0'

@tas50
Copy link
Contributor

tas50 commented Dec 15, 2015

This will be in 5.1

@tas50 tas50 closed this as completed Dec 15, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants