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 supermarket mailing list.

Select Badges

Select Supported Platforms


ops_tcpdump_handler (1) Versions 1.0.0

Installs/Configures ops_tcpdump_handler

cookbook 'ops_tcpdump_handler', '~> 1.0.0'
cookbook 'ops_tcpdump_handler', '~> 1.0.0', :supermarket
knife cookbook site install ops_tcpdump_handler
knife cookbook site download ops_tcpdump_handler

About: ops_tcpdump_handler

This cookbook is for local testing purposes only. It installs and configures tcpdump, then sets that up as a service to monitor traffic during the chef run. At the end of the run, a handler will read and print out the sniffed network traffic. Inspired by huchen.


If you are using Berkshelf for dependency resolution add an entry in your Berksfile, probably in a group: group :development do cookbook 'ops_tcpdump_handler' end

Place the cookbook at the beginning of your local run_list. For example, in vagrant:

cfg.vm.provision :chef_client do |chef|
  chef.add_recipe 'ops_tcpdump_handler'
  chef.add_recipe 'another_recipe'

Then, at the end of your run you should see something similar to:

==> node01: attempted to connect to: using http
==> node01: attempted to connect to: using http
==> node01: attempted to connect to: using https
==> node01: attempted to connect to: using https
==> node01: attempted to connect to: using https
==> node01: attempted to connect to: using https
==> node01: attempted to connect to: using https




This is for local testing only. Do not apply this cookbook to a production node.

If your cookbook relies on the runit community cookbook then any calls to the internet made by that cookbook will not show up in the logs as runit has already been configure before this service begins monitoring traffic.


Copyright 2015 Cerner Innovation, Inc.

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, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Dependent cookbooks

runit ~> 1.5.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Change Log

1.0.0 - 01-24-2016

  • [Bug] Issue-1 : Lock down version of runit cookbook

Foodcritic Metric

1.0.0 failed this metric

FC064: Ensure issues_url is set in metadata: /tmp/0013c4e18132ab6d6f44690f/ops_tcpdump_handler/metadata.rb:1
FC065: Ensure source_url is set in metadata: /tmp/0013c4e18132ab6d6f44690f/ops_tcpdump_handler/metadata.rb:1
Run with Foodcritic Version 8.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

Collaborator Number Metric

1.0.0 failed this metric

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