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


threatstack (31) Versions 3.0.2

Installs/Configures Threat Stack agent components

cookbook 'threatstack', '= 3.0.2', :supermarket
cookbook 'threatstack', '= 3.0.2'
knife supermarket install threatstack
knife supermarket download threatstack
Quality 83%

Threat Stack Cookbook

Build Status
Cookbook Version

** NOTE **: As of 3.x of this cookbook we only explicitly support version 2.x of the threatstack agent and greater.

Chef recipes to deploy the Threat Stack server agent


  • chef > 12.15


  • Amazon Linux 2
  • CentOS
  • RedHat
  • Ubuntu


The following Opscode cookbooks are dependencies:

  • apt
  • yum



Installs the Threat Stack agent package and register the agent with the service


Sets up the Apt or Yum repo for installing the Threat Stack agent package


  1. Add this cookbook to your Chef Server or add to your Berksfile

    cookbook 'threatstack', '~> 3.0.0'

  2. Add your deploy api key. The recommended way is to use an encrypted databag
    with name and item specified by the corresponding attributes. The cookbook will
    use the 'deploy_key' value from the databag by default.
    You can also set the key directly or using a wrapper cookbook in the node['threatstack']['deploy_key'] attribute.
    Setting the key will disable the encrypted data bag lookup.

Additionally you we can read the deploy key from the node.run_state['threatstack']['deploy_key'] location
Simply set the value of the deploy key in the run state at that location.

  1. Set the node['threatstack']['rulesets'] appropriately for your node(s). This attribute is an array.

  2. Add this recipe to your runlist or include in another recipe


node['threatstack']['version'] - Set to pin to a specific Threat Stack agent release version.

node['threatstack']['rulesets'] - (Required) Set this with an array of ruleset(s) to apply to the node

node['threatstack']['hostname'] - register the agent in the UI by a specific name (defaults to hostname).

node['threatstack']['ignore_failure'] - Set to true if you want the install to silently fail.

node['threatstack']['deploy_key'] - (Required) Override this with your deploy key for agent registration

node['threatstack']['data_bag_name'] - Name of the encrypted databag containing Threat Stack secrets

node['threatstack']['data_bag_item'] - Name of the encrypted databag item containing Threat Stack secrets

node['threatstack']['agent_config_args'] - Additional configuration settings for setting up agent

node['threatstack']['enable_containers'] - Set this to true in order to enable container observation. Note: container capability must already be installed and running.

Encrypted Data Bag Contents

deploy_key - the deploy key for agent registration.

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric

3.0.2 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric

3.0.2 passed this metric

Foodcritic Metric

3.0.2 passed this metric

No Binaries Metric

3.0.2 passed this metric

Testing File Metric

3.0.2 passed this metric

Version Tag Metric

3.0.2 passed this metric