Rakefile deprecation


#1

We’d like to deprecate the Rakefile because much of what it does is
superseded by knife and there is no known need to maintain both
codebases.

There are a bunch of related tickets.

CHEF-1103 - failure to upload cookbook doesn’t bubble up to the CLI
tool uploading the cookbook
CHEF-1193 - rake tasks do not carry through exit code from knife (and others?)
CHEF-1372 - rake metadata task no longer adds recipes
CHEF-1647 - rake install should not only git pull, but also git submodule update
CHEF-1748 - rake roles ignores json files
CHEF-1891 - When using rake new_cookbook, deprecation message should
show correct syntax of creating cookbook via knife tool
CHEF-1911 - As a chef user I want to load all my roles from files with
one command
CHEF-1912 - As a chef user I want to load all my data bags and items
from files with one command

Does anyone have a use case where they use rake but not knife?

Bryan


#2

Nope. Sounds like deprecation is a good idea instead of maintaining two features.

On May 10, 2011, at 10:56 AM, Bryan McLellan wrote:

We’d like to deprecate the Rakefile because much of what it does is
superseded by knife and there is no known need to maintain both
codebases.

There are a bunch of related tickets.

CHEF-1103 - failure to upload cookbook doesn’t bubble up to the CLI
tool uploading the cookbook
CHEF-1193 - rake tasks do not carry through exit code from knife (and others?)
CHEF-1372 - rake metadata task no longer adds recipes
CHEF-1647 - rake install should not only git pull, but also git submodule update
CHEF-1748 - rake roles ignores json files
CHEF-1891 - When using rake new_cookbook, deprecation message should
show correct syntax of creating cookbook via knife tool
CHEF-1911 - As a chef user I want to load all my roles from files with
one command
CHEF-1912 - As a chef user I want to load all my data bags and items
from files with one command

Does anyone have a use case where they use rake but not knife?

Bryan