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

RSS

encrypted_volume (1) Versions 0.1.0

Installs/Configures encrypted_volume

Policyfile
Berkshelf
Knife
cookbook 'encrypted_volume', '~> 0.1.0', :supermarket
cookbook 'encrypted_volume', '~> 0.1.0'
knife supermarket install encrypted_volume
knife supermarket download encrypted_volume
README
Dependencies
Quality 17%

encrypted_volume Cookbook

Encrypt your disks! Onetime, persist reboots and be restricted to host, or
persist and possibly be mountable on different hosts.

Attributes

encrypted_volume::default

  • vault - name of default chef-vault vault; where we keep the passphrases
  • mounts - hash of any mounts to encrypt. if you don't wish to use the LWRP

LWRP

  • mount_point - name_attribute - where you want to mount your volume to
  • volume - volume you want to encrypt and mount
  • fstype - filesystem to use for volume - default: ext2
  • mount_options - any special mount(5) options - default: rw
  • mode - normal, or onetime. Onetime does not save the key anywhere, effectively making the mount usable for one boot
  • vault - what chef-vault to store/get passphrase in/from
  • vault_tag - what chef-vault item to store/get the passphrase in/from. By default we generate this so that it belongs to the host. This means you can reboot to your heart's content and use the mount. Setting it to a pre-created vault item is useful for volumes you might need to move between hosts, like EBS mounts.
  • passphrase - don't use except for testing. I'm looking at you Dave.

Usage

encrypted_volume::default

If you wish to encrypt volumes based on configuration, without using
the LWRP. Just include encrypted_volume in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[encrypted_volume]"
  ],
  "default_attributes":{
    "encrypted_volume":{
      "mounts":{
        "/encrypted":{
        "volume":"/dev/sda2",
        "fstype":"ext2"
      }
    }
  }
}

LWRP

encrypted_volume "/encrypted" do
  volume      "/raw_test_volume.img"
  fstype      "ext3"
end

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  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 using Github

License and Authors

Authors: Jason Rohwedder jro@risk.io

Dependent cookbooks

chef-vault >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.1.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.1.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.1.0 failed this metric

FC064: Ensure issues_url is set in metadata: encrypted_volume/metadata.rb:1
FC065: Ensure source_url is set in metadata: encrypted_volume/metadata.rb:1
FC066: Ensure chef_version is set in metadata: encrypted_volume/metadata.rb:1
FC069: Ensure standardized license defined in metadata: encrypted_volume/metadata.rb:1
FC072: Metadata should not contain "attribute" keyword: encrypted_volume/metadata.rb:1
FC074: LWRP should use DSL to define resource's default action: encrypted_volume/resources/default.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric
            

0.1.0 passed this metric

Testing File Metric
            

0.1.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.1.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