Menu

Chef Supermarket

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.

View our collection of guides, documentation, and articles

Cookbooks
Advanced Options

Select Badges

Select Supported Platforms

Select Status

RSS

chef-guard (3) Versions 0.4.0

Installs/Configures Chef-Guard

Policyfile
Berkshelf
Knife 
cookbook 'chef-guard', '= 0.4.0', :supermarket
cookbook 'chef-guard', '= 0.4.0'
knife supermarket install chef-guard
knife supermarket download chef-guard
README
Dependencies
Changelog
Quality 29%

Chef-Guard

The Chef-Guard cookbook installs and configures Chef-Guard into your environment

Attributes

Please check http://xanzy.io/projects/chef-guard for all needed details

Usage

This cookbook uses Chef-Vault to store the .pem file content, bookshelf key, and bookshelf secret. The pem file is the private key of the Chef user that Chef-Guard uses to interact with the Chef server and Supermarket. Bookshelf is an internal component of your Chef installation and is used to store uploaded cookbook files.

Please see the following examples for creating the vault items:

knife vault create chef-guard chef.pem -M client -S "name:some-node-search" -A your-chef-username --file chef.pem

The bookshelf keys are created by Chef during install time and are saved in either /etc/chef-server/chef-server-secrets.json (for Open Source Chef) or /etc/opscode/private-chef-secrets.json (for Enterpise Chef and Chef 12) and look something like this in those files:

 "bookshelf": {
    "access_key_id": "xxxxxx",
    "secret_access_key": "yyyyyy"
 }

So just get the keys from one of those files and create the vault like this to get yourself going:

knife vault create chef-guard chef.bookshelf -M client -S "name:some-node-search" -A your-chef-username '{"key":"xxxxxx","secret":"yyyyyy"}'

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (i.e. add-new-recipe)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request

License and Authors

Authors: Sander van Harmelen (sander@xanzy.io)

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

http://www.apache.org/licenses/LICENSE-2.0

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Chef-Guard CHANGELOG

0.4.0

  • Sander van Harmelen - Updated the version attibutes to use the latest release of Chef-Guard v0.7.0. This also required updating some config attributes to remain compatible with the latest version.

0.3.5

  • Sander van Harmelen - Updated the version attibutes to use the latest release of Chef-Guard v0.6.2

0.3.4

  • Bart Groenendal - Added systemd support for CentOS / RHEL 7 and up.

0.3.3

  • Sander van Harmelen - Updated the version attibutes to use the latest release of Chef-Guard v0.6.1
  • Miguel Ferreira - Updated the foodcritic tests for better readability

0.3.2

  • Sander van Harmelen - Fixed foodcritic tests

0.3.1

  • Miguel Ferreira - Fixed syntax error in the custom foodcritic tests

0.3.0

  • Sander van Harmelen - Updated the cookbook to use Chef-Guard v0.6.0 which requires some config changes
  • Sander van Harmelen - Converted the custom Chef-Guard foodcritic file to a template. You can now add a custom regex to check for certain cookbook names and the embedded foodcritic tests will only run against matching cookbooks.

0.2.7

  • Sander Botman - Fixed the chef-guard.conf template so it includes to the 'chefclient' section

0.2.6

  • Sander van Harmelen - Updated the version attibutes to use the latest release of Chef-Guard v0.5.0
  • Sander van Harmelen - Added a new attribute for manageing the Chef clients path (new feature of Chef-Guard)

0.1.2

  • Sander van Harmelen - Changed the version attibute to point to the latest release of Chef-Guard v0.3.0

0.1.1

  • Sander van Harmelen - Improved some parts of the cookbook and added Chef-Vault logic to manage the secure items of this cookbook

0.1.0

  • Sander van Harmelen - Initial release of chef-guard-cookbook

Collaborator Number Metric 
            
0.4.0 failed this metric
Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric 
            
0.4.0 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric 
            
0.4.0 failed this metric
FC064: Ensure issues_url is set in metadata: chef-guard/metadata.rb:1
FC065: Ensure source_url is set in metadata: chef-guard/metadata.rb:1
FC066: Ensure chef_version is set in metadata: chef-guard/metadata.rb:1
FC069: Ensure standardized license defined in metadata: chef-guard/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric 
            
0.4.0 passed this metric

No Binaries Metric 
            
0.4.0 passed this metric

Testing File Metric 
            
0.4.0 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric 
            
0.4.0 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number

Sander van Harmelen Sander van Harmelen

Details

Updated September 8, 2016 Created on

Supported Platforms

  • centos >= 0.0.0
  • ubuntu >= 0.0.0
  • redhat >= 0.0.0

License

Apache 2.0

Download Cookbook