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

RSS

vault (2) Versions 0.2.0

Installs/Configures Vault

Berkshelf/Librarian
Policyfile
Knife
cookbook 'vault', '~> 0.2.0'
cookbook 'vault', '~> 0.2.0', :supermarket
knife cookbook site install vault
knife cookbook site download vault
README
Dependencies
Changelog
Quality

chef-vault

Chef cookbook for managing Vault.

In client mode, only the Vault binary will be installed.

In server mode, the binary will be installed, configured, and started as server. WARNING: The default behavior of the server is to start unconfigured. You must run vault init to generate the unseal keys and the initial root token.

Attributes

vault::default

<table> <tr> <th>Key</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>[:vault][:bin_dir]</tt></td> <td>String</td> <td>Directory to install the vault binary.</td> <td><tt>/usr/local/bin</tt></td> </tr> <tr> <td><tt>[:vault][:version]</tt></td> <td>String</td> <td>Version of Vault to install.</td> <td><tt>0.1.0</tt></td> </tr> <tr> <td><tt>[:vault][:mode]</tt></td> <td>String</td> <td>Indicates whether to install just the vault binary, or also start it as a server. Valud values are "client" and "server".</td> <td><tt>client</tt></td> </tr>

<tr> <td><tt>[:vault][:server][:config]</tt></td> <td>String</td> <td>Location of the configuration file.</td> <td><tt>/etc/vault.hcl</tt></td> </tr> <tr> <td><tt>[:vault][:server][:service_name]</tt></td> <td>String</td> <td>Name of the service as seen by the init system.</td> <td><tt>vault</tt></td> </tr> <tr> <td><tt>[:vault][:server][:init_type]</tt></td> <td>String</td> <td>Init system to run the server under. Currenly only upstart is supported.</td> <td><tt>upstart</tt></td> </tr> <tr> <td><tt>[:vault][:server][:oom_score]</tt></td> <td>Integer</td> <td>OOM score adjustment in the init config.</td> <td><tt>-100</tt></td> </tr>

<tr> <td><tt>[:vault][:server][:backends]</tt></td> <td>Hash</td> <td>Name of backends to enable along with their configurations.</td> <td><tt>{ consul: { address: "demo.consul.io:80", path: "vault" } }</tt></td> </tr> <tr> <td><tt>[:vault][:server][:listeners]</tt></td> <td>Hash</td> <td>Name of listeners to enable along with their configurations.</td> <td><tt>{ tcp: { address: "127.0.0.1:8200", tls_cert_file: "/etc/ssl/certificate.crt", tls_key_file: "/etc/ssl/key.pem" } }</tt></td> </tr> </table>

Usage

vault::default

Just include vault in your node's run_list. This will load either vault::client or vault::server depending on the value of node[:vault][:mode].

{
  "name":"my_node",
  "run_list": [
    "recipe[vault]"
  ]
}

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

vault CHANGELOG

This file is used to list changes made in each version of the vault cookbook.

0.2.0

  • Set default vault version to 0.2.0
  • Make OOM score configurable via attributes

0.1.0

  • Initial release of vault

Collaborator Number Metric
            

0.2.0 failed this metric

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

Contributing File Metric
            

0.2.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.2.0 failed this metric

FC064: Ensure issues_url is set in metadata: vault/metadata.rb:1
FC065: Ensure source_url is set in metadata: vault/metadata.rb:1
FC066: Ensure chef_version is set in metadata: vault/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.2.0 passed this metric

No Binaries Metric
            

0.2.0 passed this metric

Publish Metric
            

0.2.0 passed this metric

Supported Platforms Metric
            

0.2.0 passed this metric

Testing File Metric
            

0.2.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.2.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