vault-tree 0.3.4 → 0.6.0

data/support/cookbooks/ark/.travis.yml

@@ -1,6 +0,0 @@
-language: ruby
-gemfile:
-  - test/support/Gemfile
-rvm:
-  - 1.9.3
-script: BUNDLE_GEMFILE=test/support/Gemfile bundle exec rake foodcritic

data/support/cookbooks/ark/Berksfile

@@ -1,9 +0,0 @@
-site :opscode
-
-metadata
-
-group :integration do
-  cookbook "apt"
-  cookbook "yum"
-  cookbook "minitest-handler"
-end

data/support/cookbooks/ark/CHANGELOG.md

@@ -1,87 +0,0 @@
-ark Cookbook CHANGELOG
-======================
-This file is used to list changes made in each version of the ark cookbook.
-
-
-v0.4.0
-------
-### Improvement
-- **[COOK-3539](https://tickets.opscode.com/browse/COOK-3539)** - Allow dumping of bz2 and gzip files
-
-v0.3.2
-------
-### Bug
-- **[COOK-3191](https://tickets.opscode.com/browse/COOK-3191)** - Propogate unzip failures
-- **[COOK-3118](https://tickets.opscode.com/browse/COOK-3118)** - Set cookbook attribute in provider
-- **[COOK-3055](https://tickets.opscode.com/browse/COOK-3055)** - Use proper scope in helper module
-- **[COOK-3054](https://tickets.opscode.com/browse/COOK-3054)** - Fix notification resource updating
-
-### Improvement
-- **[COOK-3179](https://tickets.opscode.com/browse/COOK-3179)** - README updates and refactor
-
-v0.3.0
-------
-### Improvement
-
-- [COOK-3087]: Can't use ark with chef < 11
-
-### Bug
-
-- [COOK-3064]: `only_if` statements in ark's `install_with_make` and configure actions are not testing for file existence correctly.
-- [COOK-3067]: ark kitchen test for `cherry_pick` is expecting the binary to be in the same parent folder as in the archive.
-
-v0.2.4
-------
-### Bug
-
-- [COOK-3048]: Ark provider contains a `ruby_block` resource without a block attribute
-- [COOK-3063]: Ark cookbook `cherry_pick` action's unzip command does not close if statement
-- [COOK-3065]: Ark install action does not symlink binaries correctly
-
-v0.2.2
-------
-- Update the README to reflect the requirement for Chef 11 to use the ark resource (`use_inline_resources`).
-- Making this a release so it will also appear on the community site page.
-
-v0.2.0
-------
-### Bug
-
-- [COOK-2772]: Ark cookbook has foodcritic failures in provides/default.rb
-
-### Improvement
-
-- [COOK-2520]: Refactor ark providers to use the '`use_inline_resources`' LWRP DSL feature
-
-v0.1.0
-------
-- [COOK-2335] - ark resource broken on Chef 11
-
-v0.0.1
-------
-- [COOK-2026] - Allow `cherry_pick` action to be used for directories as well as files
-
-v0.0.1
-------
-- [COOK-1593] - README formatting updates for better display on Community Site
-
-v0.0.1
-------
-### Bug
-- dangling "unless"
-
-### Improvement
-- add `setup_py_*` actions
-- add vagrantfile
-- add foodcritic test
-- travis.ci support
-
-v0.0.10 (May 23, 2012
-------
-### Bug
-- `strip_leading_dir` not working for zip files https://github.com/bryanwb/chef-ark/issues/19
-
-### Improvement
-- use autogen.sh to generate configure script for configure action https://github.com/bryanwb/chef-ark/issues/16
-- support more file extensions https://github.com/bryanwb/chef-ark/pull/18
-- add extension attribute which allows you to download files which do not have the file extension as part of the URL

data/support/cookbooks/ark/CONTRIBUTING.md

@@ -1,257 +0,0 @@
-# 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.

data/support/cookbooks/ark/README.md

@@ -1,301 +0,0 @@
-# <a name="title"></a> chef-ark [![Build Status](https://secure.travis-ci.org/opscode-cookbooks/ark.png?branch=master)](https://travis-ci.org/opscode-cookbooks/ark)
-
-Overview
-========
-
-This cookbook provides `ark`, a resource for managing software
-archives. It manages the fetch-unpack-configure-build-install process
-common to installing software from source, or from binary
-distributions that are not fully fledged OS packages.
-
-This is a modified verion of Infochimp's awesome
-[install_from cookbook](http://github.com/infochimps-cookbooks/install_from).
-It has been heavily refactored and extended to meet different use
-cases.
-
-Given a simple project archive available at a url:
-
-    ark 'pig' do
-      url 'http://apache.org/pig/pig-0.8.0.tar.gz'
-    end
-
-The provider will:
-
-* fetch it to to `/var/cache/chef/`
-* unpack it to the default path  (`/usr/local/pig-0.8.0`)
-* create a symlink for `:home_dir` (`/usr/local/pig`) pointing to path
-* add specified binary commands to the enviroment `PATH` variable
-
-By default, the ark will not run again if the `:path` is not empty.
-Ark provides many actions to accommodate different use cases, such as
-`:dump`, `:cherry_pick`, `:put`, and `:install_with_make`.
-
-At this time ark only handles files available from URLs. It does not
-handle local files.
-
-Requirements
-============
-
-This cookbook requires Chef 11 for the provider, as it uses the
-`use_inline_resources` method.
-
-More about
-[use_inline_resources](http://docs.opscode.com/lwrp_common_inline_compile.html)
-in the Chef documentation.
-
-Should work on common Unix/Linux systems with typical userland
-utilities like tar, gzip, etc. May require the installation of build
-tools for compiling from source, but that installation is outside the
-scope of this cookbook.
-
-Attributes
-==========
-
-Customize the attributes to suit site specific conventions and
-defaults.
-
-* `node['ark']['apache_mirror']` - if the URL is an apache mirror,
-  use the attribute as the default.
-* `node['ark']['prefix_root']` - default base location if the
-  `prefix_root` is not passed into the resource.
-* `node['ark']['prefix_bin']` - default binary location if the
-  `prefix_bin` is not passed into the resource.
-* `node['ark']['prefix_home']` - default home location if the
-  `prefix_home` is not passed into the resource.
-
-Resources/Providers
-===================
-
-* `ark` - does the extract/build/configure dance
-
-Actions
--------
-
-- `:install`: extracts the file and creates a 'friendly' symbolic link
-  to the extracted directory path
-- `:configure`: configure ahead of the install action
-- `:install_with_make`: extracts the archive to a path, runs `make`,
-  and `make install`. It does _not_ run the configure step at this
-  time
-- `:dump`: strips all directories from the archive and dumps the
-  contained files into a specified path
-- `:cherry_pick`: extract a specified file from an archive and places
-  in specified path
-- `:put`: extract the archive to a specified path, does not create any
-  symbolic links
-- `:remove`: removes the extracted directory and related symlink #TODO
-- `:setup_py_build`: runs the command "python setup.py build" in the
-  extracted directory
-- `:setup_py_install`: runs the comand "python setup.py install" in
-  the extracted directory
-
-## :cherry_pick
-
-Extract a specified file from an archive and places in specified path.
-
-### Relevant Attribute Parameters for :cherry_pick
-
-- `path`: directory to place file in.
-- `creates`: specific file to cherry-pick.
-
-## :dump
-
-Strips all directories from the archive and dumps the contained files
-into a specified path.
-
-NOTE: This currently only works for zip archives
-
-### Attribute Parameters for :dump
-
-- `path`: path to dump files to.
-- `mode`: file mode for `app_home`, as an integer.
-  - Example: `0775`
-- `creates`: if you are appending files to a given directory, ark
-  needs a condition to test whether the file has already been
-  extracted. You can specify with creates, a file whose existence
-  indicates the ark has previously been extracted and does not need to
-  be extracted again.
-
-## :put
-
-Extract the archive to a specified path, does not create any symbolic
-links.
-
-### Attribute Parameters for :put
-
-- `path`: path to extract to.
-  - Default: `/usr/local`
-- `has_binaries`: array of binary commands to symlink into
-  `/usr/local/bin/`, you must specify the relative path.
-  - Example: `[ 'bin/java', 'bin/javaws' ]`
-- `append_env_path`: boolean, if true, append the `./bin` directory of
-  the extracted directory to the global `PATH` variable for all users.
-
-Attribute Parameters
---------------------
-
-- `name`: name of the package, defaults to the resource name.
-- `url`: url for tarball, `.tar.gz`, `.bin` (oracle-specific), `.war`,
-  and `.zip` currently supported. Also supports special syntax
-  `:name:version:apache_mirror:` that will auto-magically construct
-  download url from the apache mirrors site.
-- `version`: software version, defaults to `1`.
-- `checksum`: sha256 checksum, used for security .
-- `mode`: file mode for `app_home`, is an integer.
-- `prefix_root`: default `prefix_root`, for use with `:install*`
-  actions.
-- `prefix_home`: default directory prefix for a friendly symlink to
-  the path.
-  - Example: `/usr/local/maven` -> `/usr/local/maven-2.2.1`
-- `prefix_bin`: default directory to place a symlink to a binary
-  command.
-  - Example: `/opt/bin/mvn` -> `/opt/maven-2.2.1/bin/mvn`, where the
-    `prefix_bin` is `/opt/bin`
-- `path`: path to extract the ark to. The `:install*` actions
-  overwrite any user-provided values for `:path`.
-  - Default: `/usr/local/<name>-<version>` for the `:install`,
-    `:install_with_make` actions
-- `home_dir`: symbolic link to the path `:prefix_root/:name-:version`,
-  does not apply to `:dump`, `:put`, or `:cherry_pick` actions.
-  - Default: `:prefix_root/:name`
-- `has_binaries`: array of binary commands to symlink into
-  `/usr/local/bin/`, you must specify the relative path.
-  - Example: `[ 'bin/java', 'bin/javaws' ]`
-- `append_env_path`: boolean, similar to `has_binaries` but less
-  granular. If true, append the `./bin` directory of the extracted
-  directory to. the `PATH` environment variable for all users, by
-  placing a file in `/etc/profile.d/`. The commands are symbolically
-  linked into `/usr/bin/*`. This option provides more granularity than
-  the boolean option.
-  - Example: `mvn`, `java`, `javac`, etc.
-- `environment`: hash of environment variables to pass to invoked
-  shell commands like `tar`, `unzip`, `configure`, and `make`.
-- `strip_leading_dir`: by default, ark strips the leading directory
-  from an archive, which is the default for both `unzip` and `tar`
-  commands
-- `autoconf_opts`: an array of command line options for use with the
-  GNU `autoconf` script.
-  - Example: `[ '--include=/opt/local/include', '--force' ]`
-- `make_opts`: an array of command line options for use with `make`.
-  - Example: `[ '--warn-undefined-variables', '--load-average=2' ]`
-- `owner`: owner of extracted directory.
-  - Default: `root`
-
-### Examples
-
-This example copies `ivy.tar.gz` to
-`/var/cache/chef/ivy-2.2.0.tar.gz`, unpacks its contents to
-`/usr/local/ivy-2.2.0/` -- stripping the leading directory, and
-symlinks `/usr/local/ivy` to `/usr/local/ivy-2.2.0`
-
-     # install Apache Ivy dependency resolution tool
-     ark "ivy" do
-       url 'http://someurl.example.com/ivy.tar.gz'
-       version '2.2.0'
-       checksum '89ba5fde0c596db388c3bbd265b63007a9cc3df3a8e6d79a46780c1a39408cb5'
-       action :install
-     end
-
-This example copies `jdk-7u2-linux-x64.tar.gz` to
-`/var/cache/chef/jdk-7.2.tar.gz`, unpacks its contents to
-`/usr/local/jvm/jdk-7.2/` -- stripping the leading directory, symlinks
-`/usr/local/jvm/default` to `/usr/local/jvm/jdk-7.2`, and adds
-`/usr/local/jvm/jdk-7.2/bin/` to the global `PATH` for all users. The
-user 'foobar' is the owner of the `/usr/local/jvm/jdk-7.2` directory:
-
-     ark 'jdk' do
-       url 'http://download.example.com/jdk-7u2-linux-x64.tar.gz'
-       version '7.2'
-       path "/usr/local/jvm/"
-       home_dir "/usr/local/jvm/default"
-       checksum  '89ba5fde0c596db388c3bbd265b63007a9cc3df3a8e6d79a46780c1a39408cb5'
-       append_env_path true
-       owner 'foobar'
-     end
-
-Install Apache Ivy dependency resolution tool in <path>/resource_name in this case
-`/usr/local/ivy`, do not symlink, and strip any leading directory if one
-exists in the tarball:
-
-     ark "ivy" do
-        url 'http://someurl.example.com/ivy.tar.gz'
-        checksum '89ba5fde0c596db388c3bbd265b63007a9cc3df3a8e6d79a46780c1a39408cb5'
-        action :put
-     end
-
-Install Apache Ivy dependency resolution tool in /home/foobar/ivy, strip any
-leading directory if one exists:
-
-     ark "ivy" do
-       path "/home/foobar
-       url 'http://someurl.example.com/ivy.tar.gz'
-       checksum '89ba5fde0c596db388c3bbd265b63007a9cc3df3a8e6d79a46780c1a39408cb5'
-       action :put
-     end
-
- Strip all directories and dump files into path specified by the path attribute.
- You must specify the `creates` attribute in order to keep the extraction from
- running every time. The directory path will be created if it doesn't already exist:
-
-     ark "my_jars" do
-       url  "http://example.com/bunch_of_jars.zip"
-       path "/usr/local/tomcat/lib"
-       creates "mysql.jar"
-       owner "tomcat"
-       action :dump
-     end
-
-Extract specific files from a tarball (currently only handles one named file):
-
-     ark 'mysql-connector-java' do
-       url 'http://oracle.com/mysql-connector.zip'
-       creates 'mysql-connector-java-5.0.8-bin.jar'
-       path '/usr/local/tomcat/lib'
-       action :cherry_pick
-     end
-
-Build and install haproxy and use alternave values for `prefix_root`, `prefix_home`, and `prefix_bin`:
-
-     ark "haproxy" do
-       url  "http://haproxy.1wt.eu/download/1.5/src/snapshot/haproxy-ss-20120403.tar.gz"
-       version "1.5"
-       checksum 'ba0424bf7d23b3a607ee24bbb855bb0ea347d7ffde0bec0cb12a89623cbaf911'
-       make_opts [ 'TARGET=linux26' ]
-       prefix_root '/opt'
-       prefix_home '/opt'
-       prefix_bin  '/opt/bin'
-       action :install_with_make
-     end
-
-You can also pass multiple actions to ark and supply the file extension in case
-the file extension can not be determined by the URL:
-
-     ark "test_autogen" do
-       url 'https://github.com/zeromq/libzmq/tarball/master'
-       extension "tar.gz"
-       action [ :configure, :install_with_make ]
-     end
-
-License and Author
-==================
-
-- Author: Philip (flip) Kromer - Infochimps, Inc(<coders@infochimps.com>)
-- Author: Bryan W. Berry (<bryan.berry@gmail.com>)
-- Author: Denis Barishev (<denis.barishev@gmail.com>)
-- Author: Sean OMeara (<someara@opscode.com>)
-- Copyright: 2011, Philip (flip) Kromer - Infochimps, Inc
-- Copyright: 2012, Bryan W. Berry
-- Copyright: 2012, Denis Barishev
-- Copyright: 2013, 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.