chef 10.34.6-x86-mingw32 → 11.6.2-x86-mingw32

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    M2UwY2ViZDE4NmI5MjFkYWU3NzBhODdjMTY3NTIwZGZkZDc1ZWRhZQ==
-  data.tar.gz: !binary |-
-    ZWQxYWUxOTcxNzY5ODBjNjhmZmMwOWU3NmJjMThjZjQxNWM5NDZjNA==
+SHA1:
+  metadata.gz: 39a56000aa694e459f7e7bac62911a86d6073438
+  data.tar.gz: 9867518477423509ed26b6b8372c169cae2f783e
 SHA512:
-  metadata.gz: !binary |-
-    NWNmNDQ2YmY1MmY3M2UyYmJmNzY2NThiYmI3NTZhMzRkZTc0YThlZDgyZjJi
-    NjUwMzUwMmI2NGJlMTI2YzAzZjc5MDdlNGM4NmJmZjA0YmY5ZGY1ZTU1ZWI3
-    MTIyYWNjM2QwZGU5NTUyY2FmYWI3Zjc4MTAxMTBkNzc3YzA0MzE=
-  data.tar.gz: !binary |-
-    NmJmN2ZmMmQ0OWFmZWJlMTc2OWFkOTgzZDdjN2Q1MzkyZWIzYjE5MGMxYjZk
-    OThkYzZiNDJkMGIyY2Q5YTRkN2QxYWQ0MmM1N2NmZTY0YTZlMGFhZmQzZDI0
-    YjJiODRjNmQ3YzhlYjcyZTIwMzc1MGYxODg1ZmU3YWI0NjM2YTc=
+  metadata.gz: 9659fd46a47255b8c64527880c46927577c644571bcf58eef0799faf65012473db4935f26fd3c44deb88fb1242013d0e1479d7edc8b878b06b5c1035fc1a1e0c
+  data.tar.gz: f7cc19f73976d8623caba4c111dc11e31aa12109b100895a00a55c6040f2893d1e65dd8030cbf4834bb0bd32aa50eeb507bcac6a1f1f65e82fa7f6534b5b7269

data/CONTRIBUTING.md

@@ -0,0 +1,155 @@
+# Contributing to Chef
+
+We are glad you want to contribute to Chef! 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).
+
+## 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 chef repository by running `git clone git://github.com/opscode/chef.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.
+
+### Branches and Commits
+
+You should submit your patch as a git branch named after the ticket, such as CHEF-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.
+
+    CHEF-3435: Create deploy dirs before calling scm_provider
+        
+    The SCM providers have an assertation that requires the deploy directory to
+    exist. The deploy provider will create missing directories, we don't converge
+    the actions before we call run_action against the SCM provider, so it is not
+    yet created. This ensures we run any converge actions waiting before we call
+    the SCM provider.
+
+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 projects are available on [Github](http://www.github.com/opscode).
+
+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
+
+There are rspec unit tests in the 'spec' directory. If you don't have rspec already installed, you can use the 'bundler'
+gem to help you get the necessary prerequisites by running `sudo gem install bundler` and then `bundle install` from
+the chef respository. You can run the chef client spec tests by running `rspec spec/*` or `rake spec` from the chef 
+directory of the chef repository.
+
+These tests should pass successfully on Ruby 1.8 and 1.9 on all of the platforms that Chef runs on. It is good to run the tests 
+once on your system before you get started to ensure they all pass so you have a valid baseline. After you write your patch,
+run the tests again to see if they all pass.
+
+If any don't pass, investigate them before submitting your patch. 
+
+These tests don't modify your system, and sometimes tests fail because a command that would be run has changed because of your
+patch. This should be a simple fix. Other times the failure can show you that an important feature no longer works because of
+your change.
+
+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.
+
+## 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 update the status to _Fix Reviewed_.
+
+Depending on the project, these tickets are then merged within a week or two, depending on the current release cycle. At this
+point the ticket status will be updated to _Fix Committed_ or _Closed_.
+
+Please see the [Code Review](http://wiki.opscode.com/display/chef/Code+Review) page on the wiki for additional information.
+
+## Release Cycle
+
+The versioning for the Chef project 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
+
+Major releases and have historically been once a year. Minor releases for Chef average every two months and patch releases come as needed.
+
+There are usually beta releases and release candidates (RC) of major and minor releases announced on 
+the [chef-dev mailing list](http://lists.opscode.com/sympa/info/chef-dev). Once an RC is released, we wait at least three
+days to allow for testing for regressions before the final release. If a blocking regression is found then another RC is made containing
+the fix and the timer is reset.
+
+Once the official release is made, the release notes are available 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)
+

data/README.md

@@ -0,0 +1,89 @@
+# Chef
+
+* Documentation: [http://docs.opscode.com](http://docs.opscode.com)
+* Source: [http://github.com/opscode/chef/tree/master](http://github.com/opscode/chef/tree/master)
+* Tickets/Issues: [http://tickets.opscode.com](http://tickets.opscode.com)
+* IRC: `#chef` and `#chef-hacking` on Freenode
+* Mailing list: [http://lists.opscode.com](http://lists.opscode.com)
+
+Chef is a configuration management tool designed to bring automation to your
+entire infrastructure.
+
+The [Chef Wiki](http://wiki.opscode.com/display/chef/Home) is the definitive
+source of user documentation.
+
+This README focuses on developers who want to modify Chef source code. For
+users who just want to run the latest and greatest Chef development version in
+their environment, see the
+[Installing Chef from HEAD](http://wiki.opscode.com/display/chef/Installing+Chef+from+HEAD)
+page on the wiki.
+
+## Contributing/Development
+
+Before working on the code, if you plan to contribute your changes, you need to
+read the
+[Opscode Contributing document](http://wiki.opscode.com/display/chef/How+to+Contribute).
+
+You will also need to set up the repository with the appropriate branches. We
+document the process on the
+[Working with Git](http://wiki.opscode.com/display/chef/Working+with+git) page
+of the Chef wiki.
+
+Once your repository is set up, you can start working on the code. We do use
+TDD with RSpec, so you'll need to get a development environment running.
+
+### Requirements
+
+Ruby 1.8.7+ (As of 2012-05-25 Ruby 1.8.6 should still work, except for CHEF-2329.)
+
+### Environment
+
+In order to have a development environment where changes to the Chef code can
+be tested, we'll need to install a few things after setting up the Git
+repository.
+
+#### Non-Gem Dependencies
+
+Install these via your platform's preferred method; for example apt, yum,
+ports, emerge, etc.
+
+* [Git](http://git-scm.com/)
+* GCC and C Standard Libraries, header files, etc. (i.e., build-essential on
+debian/ubuntu)
+* Ruby development package
+
+#### Runtime Rubygem Dependencies
+
+First you'll need [bundler](http://github.com/carlhuda/bundler) which can
+be installed with a simple `gem install bundler`. Afterwords, do the following:
+
+    bundle install
+
+## Testing
+
+We use RSpec for unit/spec tests. It is not necessary to start the development
+environment to run the specs--they are completely standalone.
+
+    rake spec
+
+# License
+
+Chef - A configuration management system
+
+|                      |                                          |
+|:---------------------|:-----------------------------------------|
+| **Author:**          | Adam Jacob (<adam@opscode.com>)
+| **Copyright:**       | Copyright (c) 2008-2012 Opscode, Inc.
+| **License:**         | Apache License, Version 2.0
+
+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.

data/Rakefile

@@ -47,10 +47,12 @@ begin
   end
 rescue LoadError
   puts "sdoc is not available. (sudo) gem install sdoc to generate rdoc documentation."
+rescue TypeError
+  puts "sdoc is not working on ruby-2.0.0 and throwing an odd TypeError, rdoc generation will be disabled on ruby 2.0 until that gets fixed."
 end
 
 task :install => :package do
-  sh %{gem install pkg/#{GEM_NAME}-#{Chef::VERSION} --no-rdoc --no-ri}
+  sh %{gem install pkg/#{GEM_NAME}-#{Chef::VERSION}.gem --no-rdoc --no-ri}
 end
 
 task :uninstall do
@@ -124,5 +126,20 @@ end
 
 task :docs => "docs:all"
 
+begin
+  require 'yard'
+  DOC_FILES = [ "README.rdoc", "LICENSE", "spec/tiny_server.rb", "lib/**/*.rb" ]
+  namespace :yard do
+    desc "Create YARD documentation"
+
+    YARD::Rake::YardocTask.new(:html) do |t|
+      t.files = DOC_FILES
+      t.options = ['--format', 'html']
+    end
+  end
+
+rescue LoadError
+  puts "yard is not available. (sudo) gem install yard to generate yard documentation."
+end
 
 

data/bin/chef-apply

@@ -0,0 +1,25 @@
+#!/usr/bin/env ruby
+#
+# ./chef-apply - Run a single chef recipe
+#
+# Author:: Bryan W. Berry (<bryan.berry@gmail.com>)
+# Copyright:: Copyright (c) 2012 Bryan W. Berry
+# License:: Apache License, Version 2.0
+#
+# 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.
+
+require 'rubygems'
+$:.unshift(File.join(File.dirname(__FILE__), "..", "lib"))
+require 'chef/application/apply'
+
+Chef::Application::Apply.new.run

data/bin/chef-service-manager

@@ -0,0 +1,37 @@
+#!/usr/bin/env ruby
+#
+# ./chef-service-manager - Control chef-service on Windows platforms.
+#
+# Author:: Serdar Sutay (serdar@opscode.com)
+# Copyright:: Copyright (c) 2013 Opscode, Inc.
+# License:: Apache License, Version 2.0
+#
+# 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.
+
+require 'rubygems'
+$:.unshift(File.join(File.dirname(__FILE__), "..", "lib"))
+require 'chef'
+require 'chef/application/windows_service_manager'
+
+if Chef::Platform.windows?
+  chef_client_service = {
+    :service_name => "chef-client",
+    :service_display_name => "Chef Client Service",
+    :service_description => "Runs Opscode Chef Client on regular, configurable intervals.",
+    :service_file_path => File.expand_path(File.join(File.dirname(__FILE__), '../lib/chef/application/windows_service.rb'))
+  }
+  Chef::Application::WindowsServiceManager.new(chef_client_service).run
+else
+  puts "chef-service-manager is only available on Windows platforms."
+end
+

data/bin/chef-shell

@@ -0,0 +1,34 @@
+#!/usr/bin/env ruby
+#
+# ./chef-shell - Run the Chef REPL (Shell)
+#
+# Author:: Daniel DeLeo (<dan@kallistec.com>)
+# Copyright:: Copyright (c) 2009
+# License:: Apache License, Version 2.0
+#
+# 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.
+
+begin
+  require "rubygems"
+rescue LoadError
+end
+
+require "irb"
+require "irb/completion"
+require 'irb/ext/save-history'
+
+$:.unshift(File.expand_path(File.join(File.dirname(__FILE__), "..", "lib")))
+
+require "chef/shell"
+
+Shell.start

data/bin/shef

@@ -1,6 +1,6 @@
 #!/usr/bin/env ruby
 #
-# ./shef - Run the shef REPL
+# ./chef-shell - Run the Chef REPL (Shell)
 #
 # Author:: Daniel DeLeo (<dan@kallistec.com>)
 # Copyright:: Copyright (c) 2009
@@ -9,9 +9,9 @@
 # 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.
@@ -29,6 +29,7 @@ require 'irb/ext/save-history'
 
 $:.unshift(File.expand_path(File.join(File.dirname(__FILE__), "..", "lib")))
 
-require "chef/shef"
+require "chef/shell"
 
-Shef.start
+Chef::Log.warn("DEPRECATED: The 'shef' program is renamed to 'chef-shell'")
+Shell.start

data/distro/common/html/chef-client.8.html

@@ -124,9 +124,9 @@ wiki, http://wiki.opscode.com/display/chef/Home.</p>
 
 <h2 id="AUTHOR">AUTHOR</h2>
 
-<p>Chef was written by Adam Jacob <a href="&#x6d;&#x61;&#105;&#x6c;&#x74;&#x6f;&#58;&#97;&#100;&#x61;&#109;&#64;&#x6f;&#115;&#x70;&#99;&#111;&#x64;&#101;&#46;&#99;&#x6f;&#109;" data-bare-link="true">&#97;&#100;&#97;&#x6d;&#x40;&#x6f;&#115;&#x70;&#99;&#x6f;&#x64;&#x65;&#x2e;&#x63;&#111;&#x6d;</a> of Opscode
+<p>Chef was written by Adam Jacob <a href="&#109;&#97;&#105;&#x6c;&#116;&#111;&#58;&#x61;&#100;&#97;&#109;&#64;&#x6f;&#x73;&#x70;&#x63;&#111;&#x64;&#101;&#46;&#99;&#x6f;&#x6d;" data-bare-link="true">&#x61;&#100;&#x61;&#x6d;&#x40;&#111;&#x73;&#x70;&#99;&#111;&#x64;&#101;&#46;&#x63;&#111;&#x6d;</a> of Opscode
 (http://www.opscode.com),  with contributions from the community.  This
-manual page was written by Joshua Timberman  <a href="&#x6d;&#x61;&#x69;&#x6c;&#116;&#x6f;&#58;&#x6a;&#x6f;&#115;&#x68;&#117;&#97;&#64;&#111;&#112;&#x73;&#99;&#x6f;&#100;&#x65;&#x2e;&#x63;&#x6f;&#109;" data-bare-link="true">&#x6a;&#x6f;&#x73;&#104;&#x75;&#97;&#x40;&#111;&#112;&#x73;&#x63;&#x6f;&#x64;&#101;&#x2e;&#x63;&#x6f;&#x6d;</a>  with
+manual page was written by Joshua Timberman  <a href="&#x6d;&#97;&#105;&#x6c;&#x74;&#x6f;&#x3a;&#106;&#111;&#115;&#x68;&#117;&#x61;&#64;&#x6f;&#112;&#x73;&#99;&#x6f;&#100;&#101;&#x2e;&#x63;&#x6f;&#x6d;" data-bare-link="true">&#106;&#x6f;&#x73;&#x68;&#x75;&#97;&#64;&#x6f;&#112;&#115;&#99;&#111;&#x64;&#x65;&#46;&#x63;&#111;&#109;</a>  with
 help2man.  Permission  is  granted  to copy, distribute and / or modify
 this document under the terms of the Apache 2.0 License.</p>
 
@@ -135,8 +135,8 @@ found in /usr/share/common-licenses/Apache-2.0.</p>
 
 
   <ol class='man-decor man-foot man foot'>
-    <li class='tl'>Chef 10.34.6</li>
-    <li class='tc'>November 2014</li>
+    <li class='tl'>Chef 11.6.2</li>
+    <li class='tc'>October 2013</li>
     <li class='tr'>chef-client(8)</li>
   </ol>