Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


salt (11) Versions 1.0.0

Installs and configures Salt

cookbook 'salt', '= 1.0.0', :supermarket
cookbook 'salt', '= 1.0.0'
knife supermarket install salt
knife supermarket download salt
Quality -%


Because every Chef needs a little Salt.

Improved Remote Execution for Open Source Chef

Install Salt master and/or minion.

Why would anyone ever want to use both Salt and Chef?

I'm glad you asked!

Open Source Chef is weak in one key area that Salt just so happens to be very
strong: remote execution. knife ssh "name:*" "sudo chef-client" really doesn't
scale very well.

Think of Salt as the Push Jobs plugin for Open Source Chef. They're even based
on the same basic messaging technology: ZeroMQ.

And as of SaltStack 2014.7, they have significantly improved Chef integration.
Want to do a chef client run on all your nodes: salt "*" chef.client Then, you
can use the job management commands to check on the status of your run.

And since you made or are hopefully about to make the wise decision to use this
cookbook, you'll get even better Chef-Salt integration. The cookbook will
automatically sync up the metadata (grains in Salt parlance) between Chef and
Salt to allow you to filter on role or environment or custom markers.



This cooked has been confirmed to work on:

  • Ubuntu 10.04 or later
  • CentOS 5+, RedHat 5+, Scientific Linux 5+
  • Fedora 19, 20
  • Debian 7 (Wheezy)


  • apt
  • yum
  • yum-epel


  • node['salt']['version'] - Package version to be installed (defaults to nil for latest). This attribute applies to both the master and minion, since you'll want to keep their versions synced up
  • node['salt']['role']['master'] - Salt master role (defaults to salt_master)
  • node['salt']['role']['minion'] - Salt minion role (defaults to salt_minion)


  • node['salt']['minion']['master'] - Address or list of masters, if not using built-in search functionality.
  • node['salt']['minion']['environment'] - The environment in which to search for a master; or nil to search all environments (defaults to the node's environment)
  • node['salt']['minion']['grains'] - Map of custom grains for tagging the minion. Each entry may contain a single string value or a list of strings.
  • node['salt']['minion']['config_cookbook'] and node['salt']['minion']['config_template'] allow you to override the template used to generate the minion config file /etc/salt/minion


  • node['salt']['minion']['environment'] - The environment in which to search for minions; or nil to search all environments (defaults to the node's environment)
  • node['salt']['master']['config_cookbook'] and node['salt']['master']['config_template'] allow you to override the template used to generate the master config file /etc/salt/master

See attribute files for more supported attributes.



Nothing; reserved to include future LWRPs.


Install Salt master using OS package manager.


Install Salt master using OS package manager.


None at this time.


Define two roles named salt_master and salt_minion, which include the corresponding
recipes. The nodes will automatically discover each other within the same environment
(when using Chef Server).

If you want your Salt Masters to operate across all environments, set
node['salt']['minion']['environment'] to nil for all minions; and set
node['salt']['master']['environment'] to nil for all masters.

The cookbook will automatically manage the key exchange between minions and masters.
Note that once a new minion is setup, it will still be unable to communicate with the master(s)
until the next Chef run on the master(s). The minion recipe registers the minion's public key
and the master recipe then accepts any new keys that are registered with Chef.

Using Salt

Targetting Minions

This cookbook attempts to keep metadata synchronized between Chef and Salt.

Minions are automatically tagged (and updated on every chef-client run) with the
following two standard Salt grains:

  • environment contains the chef environment of the node: salt -G "environment:production" ...
  • role contains a complete expanded list of roles assigned to the node (this includes roles within roles): salt -G "role:salt_minion" ...

In addition, you can define your own custom grains using the node['salt']['minion']['grains'] attribute. See above.

License and Author

Author:: Daryl Robbins

Copyright:: 2014, Daryl Robbins

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

apt ~> 2.3.10
yum ~> 3.0
yum-epel >= 0.0.0
ohai >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

CHANGELOG for Salt Cookbook

This file is used to list changes made in each version of the Salt Cookbook


  • Add support for key exchange between minions and master
  • node['salt']['minion']['master_environment'] has been renamed to node['salt']['minion']['environment'] now that the master end of the discovery process has been implemented.

No quality metric results found