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

rack_user (5) Versions 0.0.1

Installs/Configures rack_user

Policyfile
Berkshelf
Knife
cookbook 'rack_user', '= 0.0.1', :supermarket
cookbook 'rack_user', '= 0.0.1'
knife supermarket install rack_user
knife supermarket download rack_user
README
Dependencies
Changelog
Quality 0%

Circle CI

rack_user-cookbook

The Rackspace rack_user cookbook provides resource primitives (LWRPs) for use in recipes.
The goal is to offer a resource to add a rack user with a list of authorized keys and sudo access.
Currently it only supports to get keys from a remote file, but it might be extended later.

Supported Platforms

  • Centos 6.5
  • Ubuntu 12.04
  • Ubuntu 14.04

Usage

Place a dependency on the rack_user cookbook in your cookbook's metadata.rb

depends 'rack_user'

Then, in a recipe:

rack_user 'default' do
  action :create
end

Resources

rack_user

The rack_user resource creates a rack user with a list of authorized keys.

Parameters

Actions

  • :create - Create the rack user
  • :remove - remove the rack user

Examples

Create the user with an authorized key file from a gist

rack_user 'default' do
  location 'https://gist.githubusercontent.com/dummy_user/af613872c3d029a94c88/raw/1d57582215ac6316f55b956691db1dba8339fcdd/test'
end

Remove the user

rack_user 'default' do
  action :remove
end

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

Author:: Julien Berard (jujugrrr@gmail.com)

rack_user CHANGELOG

0.1.0

Foodcritic Metric
            

0.0.1 failed this metric

FC031: Cookbook without metadata file: /tmp/cook/769712222cd24ff91b5a8162/rack_user/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/769712222cd24ff91b5a8162/rack_user/metadata.rb:1