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

sudo_rules (6) Versions 0.1.3

Configures sudo rules from data bags using the sudo cookbook

Berkshelf/Librarian
Policyfile
Knife
cookbook 'sudo_rules', '= 0.1.3'
cookbook 'sudo_rules', '= 0.1.3', :supermarket
knife cookbook site install sudo_rules
knife cookbook site download sudo_rules
README
Dependencies
Changelog
Quality 0%

sudo_rules Cookbook

Reads through a special data bag of sudo rules to compile a list of sudoers.d rules to create/remove.

Requirements

packages

  • sudo

Attributes

sudo_rules::default

Key Type Description Default
['sudo_rules'] String Name of data bag to use for entries. sudo_rules

data bag

Key Type Description Default Required?
id String Name of Data Bag item, and sudoers.d/Id filename. None Yes
name String Instead of using Id, you can choose the name of the file for sudoers.d/Name instead. Same as Id No
hosts Array List of hosts to apply this rule to by fqdn, can be wildcard matched. [] Yes
action String create or remove Sets whether to create or remove the entry. create No
user String Username or %Groupname to use for the sudo rule. None Yes
runas String Allowed colon-separated list of users for sudoers runas. ALL No
commands Array List of commands (and arguments) this rule adds for the user/group. [] Yes
defaults Array List of defaults this user has. [] No

Usage

sudo_rules::default

Include sudo_rules in your node's run_list:

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

And provide properly formatted data bag:

{
    "id": "Data Bag unique name, default value for name below",
    "name": "Name of the sudoers.d file",
    "hosts": [
        "fqdn1",
        "fqdn2",
        ...
    ],
    "action": "create",
    "user": "someuser",
    "runas": "ALL",
    "commands": [
        "/usr/sbin/somecommand args",
        "/usr/sbin/anothercommand",
        ...
    ],
    "defaults": [
        "env_reset"
    ]
}

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

or

  1. Report issue on Github

License and Authors

Authors: Eric Renfro erenfro@linux-help.org

Dependent cookbooks

sudo >= 2.7.1

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

sudo_rules CHANGELOG

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

0.1.3

  • [erenfro] - LICENSE added.

0.1.2

  • [erenfro] - Code cleanup, documentation cleanup.

0.1.1

  • [erenfro] - Cleanup typos.

0.1.0

  • [erenfro] - Initial release of sudo_rules

Check the Markdown Syntax Guide for help with Markdown.

The Github Flavored Markdown page describes the differences between markdown on github and standard markdown.

Foodcritic Metric
            

0.1.3 failed this metric

FC031: Cookbook without metadata file: /tmp/cook/d7da3897a5fb4f30106bb9b5/sudo_rules/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/d7da3897a5fb4f30106bb9b5/sudo_rules/metadata.rb:1