berks

Install cookbook dependencies

$ berks install

$ berks update [cookbook-name]

$ berks upload

$ berks package [output.tar.gz]

$ berks list

$ berks outdated

$ berks viz

$ berks info [cookbook-name]

berks subcommand [options]

berks (Berkshelf) is a dependency manager for Chef cookbooks. It resolves and manages cookbook dependencies defined in a Berksfile, similar to how Bundler manages Ruby gems.
Berkshelf ensures consistent cookbook versions across development, testing, and production environments. It can fetch cookbooks from the Chef Supermarket, Git repositories, or local paths.

--format value

Output format: human (default), json, null

Path to the Berksfile

Exclude cookbook groups

Include only specified groups

Suppress output

Enable debug output

install

Install cookbooks into the local cache based on Berksfile.lock

Update one or all cookbook dependencies

Upload resolved cookbooks to the Chef Infra Server

Package cookbook dependencies into a tar archive

List cookbooks and their dependencies

Show cookbooks with newer versions available

Generate a dependency graph image

Display metadata for a specific cookbook

Apply version locks to a Chef environment

Vendor cookbooks into a local directory

Display Berkshelf version

Berkshelf is deprecated and no longer actively maintained. New users should use Policyfiles instead, which is the recommended approach for managing Chef cookbook dependencies. Existing Berkshelf users are encouraged to migrate.

Berkshelf was created by Jamie Winsor and Seth Vargo in 2012 to solve Chef cookbook dependency management. It became part of the Chef Development Kit (ChefDK) and later Chef Workstation. Chef announced Policyfiles as the successor in 2015.

chef(1), knife(1), kitchen(1)