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


ipaddr_extensions (4) Versions 0.3.0

Adds the ipaddr_extensions gem to chef

cookbook 'ipaddr_extensions', '= 0.3.0', :supermarket
cookbook 'ipaddr_extensions', '= 0.3.0'
knife supermarket install ipaddr_extensions
knife supermarket download ipaddr_extensions
Quality -%


Adds the ipaddr_extensions gem to chef using the chef_gem provider. This adds a
top-level ohai attribute called privateaddress. If there is an RFC1918 IP address,
this is assigned to node.privateaddress.


Include ipaddr_extensions in your Berksfile or Cheffile:

cookbook 'ipaddr_extensions'

Include ipaddr_extensions in your node's run_list:

  "run_list": [

If a cookbook depends on knowing about private ip addresses, depend or suggest this cookbook.

include_recipe 'ipaddr_extensions'


This cookbook does terrible things that should never ever be done in
Chef, nor in Ruby for that matter. It should only do this once, after
which the ipaddr_extensions gem will be installed and working. There
are so many reasons this could go wrong, though.

Running tests

This cookbook runs assertions as a part of a fake cookbook using

bundle exec kitchen converge

The test suite depends on network bridging in vagrant. This requires an
exact match of the interface name in order to work. If you run into
trouble, temporarily change .kitchen.yml#L12 to match the name of your
ethernet adapter.


  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write you change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

No quality metric results found