guard-strainer 1.0.0

data/spec/fixtures/cookbooks/sudo/attributes/default.rb

@@ -0,0 +1,25 @@
+#
+# Cookbook Name:: sudo
+# Attribute File:: default
+#
+# Copyright 2008-2011, Opscode, Inc.
+#
+# 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
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+default['authorization']['sudo']['groups']            = []
+default['authorization']['sudo']['users']             = []
+default['authorization']['sudo']['passwordless']      = false
+default['authorization']['sudo']['include_sudoers_d'] = false
+default['authorization']['sudo']['agent_forwarding']  = false
+default['authorization']['sudo']['sudoers_defaults']  = ['!lecture,tty_tickets,!fqdn']

data/spec/fixtures/cookbooks/sudo/files/default/README

@@ -0,0 +1,17 @@
+#
+# As of Debian version 1.7.2p1-1, the default /etc/sudoers file created on
+# installation of the package now includes the directive:
+#
+#       #includedir /etc/sudoers.d
+#
+# This will cause sudo to read and parse any files in the /etc/sudoers.d
+# directory that do not end in '~' or contain a '.' character.
+#
+# Note that there must be at least one file in the sudoers.d directory (this
+# one will do), and all files in this directory should be mode 0440.
+#
+# Note also, that because sudoers contents can vary widely, no attempt is
+# made to add this directive to existing sudoers files on upgrade.  Feel free
+# to add the above directive to the end of your /etc/sudoers file to enable
+# this functionality for existing installations if you wish!
+#

data/spec/fixtures/cookbooks/sudo/metadata.rb

@@ -0,0 +1,46 @@
+name              'sudo'
+maintainer        'Opscode, Inc.'
+maintainer_email  'cookbooks@opscode.com'
+license           'Apache 2.0'
+description       'Installs sudo and configures /etc/sudoers'
+version           '2.1.5'
+
+recipe 'sudo', 'Installs sudo and configures /etc/sudoers'
+
+%w{redhat centos fedora ubuntu debian freebsd}.each do |os|
+  supports os
+end
+
+attribute 'authorization',
+  :display_name => 'Authorization',
+  :description => 'Hash of Authorization attributes',
+  :type => 'hash'
+
+attribute 'authorization/sudo',
+  :display_name => 'Authorization Sudoers',
+  :description => 'Hash of Authorization/Sudo attributes',
+  :type => 'hash'
+
+attribute 'authorization/sudo/users',
+  :display_name => 'Sudo Users',
+  :description => 'Users who are allowed sudo ALL',
+  :type => 'array',
+  :default => ''
+
+attribute 'authorization/sudo/groups',
+  :display_name => 'Sudo Groups',
+  :description => 'Groups who are allowed sudo ALL',
+  :type => 'array',
+  :default => ''
+
+attribute 'authorization/sudo/passwordless',
+  :display_name => 'Passwordless Sudo',
+  :description => '',
+  :type => 'string',
+  :default => 'false'
+
+attribute 'authorization/sudo/include_sudoers_d',
+  :display_name => 'Include sudoers.d',
+  :description => 'Whether to create the sudoers.d includedir',
+  :type => 'string',
+  :default => 'false'

data/spec/fixtures/cookbooks/sudo/providers/default.rb

@@ -0,0 +1,135 @@
+#
+# Author:: Bryan W. Berry (<bryan.berry@gmail.com>)
+# Author:: Seth Vargo (<sethvargo@gmail.com>)
+# Cookbook Name:: sudo
+# Provider:: default
+#
+# Copyright 2011, Bryan w. Berry
+# Copyright 2012, Seth Vargo
+#
+# 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
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+# This LWRP supports whyrun mode
+def whyrun_supported?
+  true
+end
+
+# Ensure that the inputs are valid (we cannot just use the resource for this)
+def check_inputs(user, group, foreign_template, foreign_vars)
+  # if group, user, and template are nil, throw an exception
+  if user == nil && group == nil && foreign_template == nil
+    Chef::Application.fatal!('You must provide a user, group, or template!')
+  elsif user != nil && group != nil && template != nil
+    Chef::Application.fatal!('You cannot specify user, group, and template!')
+  end
+end
+
+# Validate the given resource (template) by writing it out to a file and then
+# ensuring that file's contents pass `visudo -c`
+def validate_fragment!(resource)
+  file = Tempfile.new('sudoer')
+
+  begin
+    file.write(capture(resource))
+
+    cmd = Mixlib::ShellOut.new("visudo -cf #{file.path}").run_command
+    unless cmd.exitstatus == 0
+      Chef::Log.error("Fragment validation failed: \n\n")
+      Chef::Log.error(file.read)
+      Chef::Application.fatal!("Template #{file.path} failed fragment validation!")
+    end
+  ensure
+    file.close
+    file.unlink
+  end
+end
+
+# Render a single sudoer template. This method has two modes:
+#   1. using the :template option - the user can specify a template
+#      that exists in the local cookbook for writing out the attributes
+#   2. using the built-in template (recommended) - simply pass the
+#      desired variables to the method and the correct template will be
+#      written out for the user
+def render_sudoer
+  if new_resource.template
+    Chef::Log.debug('Template attribute provided, all other attributes ignored.')
+
+    resource = template "/etc/sudoers.d/#{new_resource.name}" do
+      source        new_resource.template
+      owner         'root'
+      group         'root'
+      mode          '0440'
+      variables     new_resource.variables
+      action        :nothing
+    end
+  else
+    sudoer = new_resource.user || "%#{new_resource.group}".squeeze('%')
+
+    resource = template "/etc/sudoers.d/#{new_resource.name}" do
+      source        'sudoer.erb'
+      cookbook      'sudo'
+      owner         'root'
+      group         'root'
+      mode          '0440'
+      variables     :sudoer => sudoer,
+                    :host => new_resource.host,
+                    :runas => new_resource.runas,
+                    :nopasswd => new_resource.nopasswd,
+                    :commands => new_resource.commands
+      action        :nothing
+    end
+  end
+
+  # Ensure that, adding this sudoer, would not break sudo
+  validate_fragment!(resource)
+
+  resource.run_action(:create)
+  new_resource.updated_by_last_action(true) if resource.updated_by_last_action?
+end
+
+# Default action - install a single sudoer
+action :install do
+  render_sudoer
+end
+
+# Removes a user from the sudoers group
+action :remove do
+  resource = file "/etc/sudoers.d/#{new_resource.name}" do
+    action :nothing
+  end
+  resource.run_action(:delete)
+  new_resource.updated_by_last_action(true) if resource.updated_by_last_action?
+end
+
+private
+# Capture a template to a string
+def capture(template)
+  context = {}
+  context.merge!(template.variables)
+  context[:node] = node
+
+  eruby = Erubis::Eruby.new(::File.read(template_location(template)))
+  return eruby.evaluate(context)
+end
+
+# Find the template
+def template_location(template)
+  if template.local
+    template.source
+  else
+    context = template.instance_variable_get('@run_context')
+    cookbook = context.cookbook_collection[template.cookbook || template.cookbook_name]
+    cookbook.preferred_filename_on_disk_location(node, :templates, template.source)
+  end
+end

data/spec/fixtures/cookbooks/sudo/recipes/default.rb

@@ -0,0 +1,54 @@
+#
+# Cookbook Name:: sudo
+# Recipe:: default
+#
+# Copyright 2008-2011, Opscode, Inc.
+#
+# 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
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+package 'sudo' do
+  action :install
+end
+
+if node['authorization']['sudo']['include_sudoers_d']
+  directory '/etc/sudoers.d' do
+    mode        '0755'
+    owner       'root'
+    group       'root'
+    action      :create
+  end
+
+  cookbook_file '/etc/sudoers.d/README' do
+    source      'README'
+    mode        '0440'
+    owner       'root'
+    group       'root'
+    action      :create
+  end
+end
+
+template '/etc/sudoers' do
+  source 'sudoers.erb'
+  mode '0440'
+  owner 'root'
+  group platform?('freebsd') ? 'wheel' : 'root'
+  variables(
+    :sudoers_groups => node['authorization']['sudo']['groups'],
+    :sudoers_users => node['authorization']['sudo']['users'],
+    :passwordless => node['authorization']['sudo']['passwordless'],
+    :include_sudoers_d => node['authorization']['sudo']['include_sudoers_d'],
+    :agent_forwarding => node['authorization']['sudo']['agent_forwarding'],
+    :sudoers_defaults => node['authorization']['sudo']['sudoers_defaults']
+  )
+end

data/spec/fixtures/cookbooks/sudo/resources/default.rb

@@ -0,0 +1,38 @@
+#
+# Author:: Bryan W. Berry (<bryan.berry@gmail.com>)
+# Cookbook Name:: sudo
+# Resource:: default
+#
+# Copyright 2011, Bryan w. Berry
+#
+# 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
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+actions :install, :remove
+default_action :install
+
+attribute :user,       :kind_of => String,          :default => nil
+attribute :group,      :kind_of => String,          :default => nil
+attribute :commands,   :kind_of => Array,           :default => ['ALL']
+attribute :host,       :kind_of => String,          :default => 'ALL'
+attribute :runas,      :kind_of => String,          :default => 'ALL'
+attribute :nopasswd,   :equal_to => [true, false],  :default => false
+attribute :template,   :regex => /^[a-z_]+.erb$/,   :default => nil
+attribute :variables,  :kind_of => Hash,            :default => nil
+
+# Set default for the supports attribute in initializer since it is
+# a 'reserved' attribute name
+def initialize(*args)
+  super
+  @action = :install
+  @supports = { :report => true, :exception => true }
+end

data/spec/fixtures/cookbooks/sudo/templates/default/sudoer.erb

@@ -0,0 +1,6 @@
+# This file is managed by Chef.
+# Do NOT modify this file directly.
+
+<% @commands.each do |command| -%>
+<%= @sudoer %>  <%= @host %>=(<%= @runas %>) <%= 'NOPASSWD:' if @nopasswd %><%= command %>
+<% end -%>

data/spec/fixtures/cookbooks/sudo/templates/default/sudoers.erb

@@ -0,0 +1,26 @@
+# This file is managed by Chef.
+# Do NOT modify this file directly.
+
+<% @sudoers_defaults.each do |defaults| -%>
+Defaults      <%= defaults %>
+<% end -%>
+<% if @agent_forwarding -%>
+Defaults      env_keep+=SSH_AUTH_SOCK
+<% end -%>
+
+# User privilege specification
+root          ALL=(ALL) ALL
+
+<% @sudoers_users.each do |user| -%>
+<%= user %>   ALL=(ALL) <%= "NOPASSWD:" if @passwordless %>ALL
+<% end -%>
+
+# Members of the sysadmin group may gain root privileges
+%sysadmin     ALL=(ALL) <%= "NOPASSWD:" if @passwordless %>ALL
+
+<% @sudoers_groups.each do |group| -%>
+# Members of the group '<%= group %>' may gain root privileges
+%<%= group %> ALL=(ALL) <%= "NOPASSWD:" if @passwordless %>ALL
+<% end -%>
+
+<%= '#includedir /etc/sudoers.d' if @include_sudoers_d  %>

data/spec/fixtures/cookbooks/tmux/.chef/knife.rb

@@ -0,0 +1,2 @@
+cache_type 'BasicFile'
+cache_options(:path => "#{ENV['HOME']}/.chef/checksums")

data/spec/fixtures/cookbooks/tmux/.gitignore

@@ -0,0 +1 @@
+tmp

data/spec/fixtures/cookbooks/tmux/.travis.yml

@@ -0,0 +1,7 @@
+language: ruby
+rvm:
+  - 1.9.2
+  - 1.9.3
+script:
+  - bundle exec rake knife
+  - bundle exec rake foodcritic

data/spec/fixtures/cookbooks/tmux/CHANGELOG.md

@@ -0,0 +1,39 @@
+## v1.3.0:
+
+### Improvement
+
+- [COOK-2547]: Add more options to tmux.conf template
+
+## v1.2.2:
+
+The repository didn't have pushed commits, and so the following
+changes from earlier-than-latest versions wouldn't be available on the
+community site. We're releasing 1.2.2 to correct this.
+
+* [COOK-1841] - recipe downloads tmux tar everytime, even if its
+  installed
+
+## v1.2.0:
+
+* [COOK-1649] - Typo in tmux default attributes
+* [COOK-1652] - Missing deps for building tmux on centos
+* [COOK-1756] - Allow tmux to be installed via source or package based
+  on attribute
+
+## v1.1.2:
+
+* [COOK-1841] - recipe downloads tmux tar everytime, even if its
+  installed
+
+## v1.1.0:
+
+* Added test-kitchen support
+
+## v1.0.1:
+
+* Add test kitchen support (test directory not included in release to community site)
+* [COOK-1366] - default config template, TravisCI and CentOS support
+
+## v1.0.0:
+
+* Initial Release

data/spec/fixtures/cookbooks/tmux/CONTRIBUTING.md

@@ -0,0 +1,257 @@
+# Contributing to Opscode Cookbooks
+
+We are glad you want to contribute to Opscode Cookbooks! The first
+step is the desire to improve the project.
+
+You can find the answers to additional frequently asked questions
+[on the wiki](http://wiki.opscode.com/display/chef/How+to+Contribute).
+
+You can find additional information about
+[contributing to cookbooks](http://wiki.opscode.com/display/chef/How+to+Contribute+to+Opscode+Cookbooks)
+on the wiki as well.
+
+## Quick-contribute
+
+* Create an account on our [bug tracker](http://tickets.opscode.com)
+* Sign our contributor agreement (CLA)
+[ online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L)
+(keep reading if you're contributing on behalf of your employer)
+* Create a ticket for your change on the
+  [bug tracker](http://tickets.opscode.com)
+* Link to your patch as a rebased git branch or pull request from the
+  ticket
+* Resolve the ticket as fixed
+
+We regularly review contributions and will get back to you if we have
+any suggestions or concerns.
+
+## The Apache License and the CLA/CCLA
+
+Licensing is very important to open source projects, it helps ensure
+the software continues to be available under the terms that the author
+desired. Chef uses the Apache 2.0 license to strike a balance between
+open contribution and allowing you to use the software however you
+would like to.
+
+The license tells you what rights you have that are provided by the
+copyright holder. It is important that the contributor fully
+understands what rights they are licensing and agrees to them.
+Sometimes the copyright holder isn't the contributor, most often when
+the contributor is doing work for a company.
+
+To make a good faith effort to ensure these criteria are met, Opscode
+requires a Contributor License Agreement (CLA) or a Corporate
+Contributor License Agreement (CCLA) for all contributions. This is
+without exception due to some matters not being related to copyright
+and to avoid having to continually check with our lawyers about small
+patches.
+
+It only takes a few minutes to complete a CLA, and you retain the
+copyright to your contribution.
+
+You can complete our contributor agreement (CLA)
+[ online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L).
+If you're contributing on behalf of your employer, have your employer
+fill out our
+[Corporate CLA](https://secure.echosign.com/public/hostedForm?formid=PIE6C7AX856)
+instead.
+
+## Ticket Tracker (JIRA)
+
+The [ticket tracker](http://tickets.opscode.com) is the most important
+documentation for the code base. It provides significant historical
+information, such as:
+
+* Which release a bug fix is included in
+* Discussion regarding the design and merits of features
+* Error output to aid in finding similar bugs
+
+Each ticket should aim to fix one bug or add one feature.
+
+## Using git
+
+You can get a quick copy of the repository for this cookbook by
+running `git clone
+git://github.com/opscode-coobkooks/COOKBOOKNAME.git`.
+
+For collaboration purposes, it is best if you create a Github account
+and fork the repository to your own account. Once you do this you will
+be able to push your changes to your Github repository for others to
+see and use.
+
+If you have another repository in your GitHub account named the same
+as the cookbook, we suggest you suffix the repository with -cookbook.
+
+### Branches and Commits
+
+You should submit your patch as a git branch named after the ticket,
+such as COOK-1337. This is called a _topic branch_ and allows users to
+associate a branch of code with the ticket.
+
+It is a best practice to have your commit message have a _summary
+line_ that includes the ticket number, followed by an empty line and
+then a brief description of the commit. This also helps other
+contributors understand the purpose of changes to the code.
+
+    [COOK-1757] - platform_family and style
+
+    * use platform_family for platform checking
+    * update notifies syntax to "resource_type[resource_name]" instead of
+      resources() lookup
+    * COOK-692 - delete config files dropped off by packages in conf.d
+    * dropped debian 4 support because all other platforms have the same
+      values, and it is older than "old stable" debian release
+
+Remember that not all users use Chef in the same way or on the same
+operating systems as you, so it is helpful to be clear about your use
+case and change so they can understand it even when it doesn't apply
+to them.
+
+### Github and Pull Requests
+
+All of Opscode's open source cookbook projects are available on
+[Github](http://www.github.com/opscode-cookbooks).
+
+We don't require you to use Github, and we will even take patch diffs
+attached to tickets on the tracker. However Github has a lot of
+convenient features, such as being able to see a diff of changes
+between a pull request and the main repository quickly without
+downloading the branch.
+
+If you do choose to use a pull request, please provide a link to the
+pull request from the ticket __and__ a link to the ticket from the
+pull request. Because pull requests only have two states, open and
+closed, we can't easily filter pull requests that are waiting for a
+reply from the author for various reasons.
+
+### More information
+
+Additional help with git is available on the
+[Working with Git](http://wiki.opscode.com/display/chef/Working+with+Git)
+wiki page.
+
+## Functional and Unit Tests
+
+This cookbook is set up to run tests under
+[Opscode's test-kitchen](https://github.com/opscode/test-kitchen). It
+uses minitest-chef to run integration tests after the node has been
+converged to verify that the state of the node.
+
+Test kitchen should run completely without exception using the default
+[baseboxes provided by Opscode](https://github.com/opscode/bento).
+Because Test Kitchen creates VirtualBox machines and runs through
+every configuration in the Kitchenfile, it may take some time for
+these tests to complete.
+
+If your changes are only for a specific recipe, run only its
+configuration with Test Kitchen. If you are adding a new recipe, or
+other functionality such as a LWRP or definition, please add
+appropriate tests and ensure they run with Test Kitchen.
+
+If any don't pass, investigate them before submitting your patch.
+
+Any new feature should have unit tests included with the patch with
+good code coverage to help protect it from future changes. Similarly,
+patches that fix a bug or regression should have a _regression test_.
+Simply put, this is a test that would fail without your patch but
+passes with it. The goal is to ensure this bug doesn't regress in the
+future. Consider a regular expression that doesn't match a certain
+pattern that it should, so you provide a patch and a test to ensure
+that the part of the code that uses this regular expression works as
+expected. Later another contributor may modify this regular expression
+in a way that breaks your use cases. The test you wrote will fail,
+signalling to them to research your ticket and use case and accounting
+for it.
+
+If you need help writing tests, please ask on the Chef Developer's
+mailing list, or the #chef-hacking IRC channel.
+
+## Code Review
+
+Opscode regularly reviews code contributions and provides suggestions
+for improvement in the code itself or the implementation.
+
+We find contributions by searching the ticket tracker for _resolved_
+tickets with a status of _fixed_. If we have feedback we will reopen
+the ticket and you should resolve it again when you've made the
+changes or have a response to our feedback. When we believe the patch
+is ready to be merged, we will tag the _Code Reviewed_ field with
+_Reviewed_.
+
+Depending on the project, these tickets are then merged within a week
+or two, depending on the current release cycle.
+
+## Release Cycle
+
+The versioning for Opscode Cookbook projects is X.Y.Z.
+
+* X is a major release, which may not be fully compatible with prior
+  major releases
+* Y is a minor release, which adds both new features and bug fixes
+* Z is a patch release, which adds just bug fixes
+
+A released version of a cookbook will end in an even number, e.g.
+"1.2.4" or "0.8.0". When development for the next version of the
+cookbook begins, the "Z" patch number is incremented to the next odd
+number, however the next release of the cookbook may be a major or
+minor incrementing version.
+
+Releases of Opscode's cookbooks are usually announced on the Chef user
+mailing list. Releases of several cookbooks may be batched together
+and announced on the [Opscode Blog](http://www.opscode.com/blog).
+
+## Working with the community
+
+These resources will help you learn more about Chef and connect to
+other members of the Chef community:
+
+* [chef](http://lists.opscode.com/sympa/info/chef) and
+  [chef-dev](http://lists.opscode.com/sympa/info/chef-dev) mailing
+  lists
+* #chef and #chef-hacking IRC channels on irc.freenode.net
+* [Community Cookbook site](http://community.opscode.com)
+* [Chef wiki](http://wiki.opscode.com/display/chef)
+* Opscode Chef [product page](http://www.opscode.com/chef)
+
+
+## Cookbook Contribution Do's and Don't's
+
+Please do include tests for your contribution. If you need help, ask
+on the
+[chef-dev mailing list](http://lists.opscode.com/sympa/info/chef-dev)
+or the
+[#chef-hacking IRC channel](http://community.opscode.com/chat/chef-hacking).
+Not all platforms that a cookbook supports may be supported by Test
+Kitchen. Please provide evidence of testing your contribution if it
+isn't trivial so we don't have to duplicate effort in testing. Chef
+10.14+ "doc" formatted output is sufficient.
+
+Please do indicate new platform (families) or platform versions in the
+commit message, and update the relevant ticket.
+
+If a contribution adds new platforms or platform versions, indicate
+such in the body of the commit message(s), and update the relevant
+COOK ticket. When writing commit messages, it is helpful for others if
+you indicate the COOK ticket. For example:
+
+    git commit -m '[COOK-1041] - Updated pool resource to correctly
+    delete.'
+
+Please do use [foodcritic](http://acrmp.github.com/foodcritic) to
+lint-check the cookbook. Except FC007, it should pass all correctness
+rules. FC007 is okay as long as the dependent cookbooks are *required*
+for the default behavior of the cookbook, such as to support an
+uncommon platform, secondary recipe, etc.
+
+Please do ensure that your changes do not break or modify behavior for
+other platforms supported by the cookbook. For example if your changes
+are for Debian, make sure that they do not break on CentOS.
+
+Please do not modify the version number in the metadata.rb, Opscode
+will select the appropriate version based on the release cycle
+information above.
+
+Please do not update the CHANGELOG.md for a new version. Not all
+changes to a cookbook may be merged and released in the same versions.
+Opscode will update the CHANGELOG.md when releasing a new version of
+the cookbook.