berkshelf 7.0.7 → 7.0.8

data/Thorfile

@@ -1,61 +0,0 @@
-# encoding: utf-8
-$:.unshift File.expand_path("../lib", __FILE__)
-
-require "bundler"
-require "thor/rake_compat"
-
-class Gem < Thor
-  include Thor::RakeCompat
-  Bundler::GemHelper.install_tasks
-
-  desc "build", "Build berkshelf-#{Berkshelf::VERSION}.gem into the pkg directory"
-  def build
-    Rake::Task["build"].execute
-  end
-
-  desc "install", "Build and install berkshelf-#{Berkshelf::VERSION}.gem into system gems"
-  def install
-    Rake::Task["install"].execute
-  end
-
-  desc "release", "Create tag v#{Berkshelf::VERSION} and build and push berkshelf-#{Berkshelf::VERSION}.gem to Rubygems"
-  def release
-    Rake::Task["release"].execute
-  end
-end
-
-class Spec < Thor
-  include Thor::Actions
-  default_task :all
-
-  desc "all", "Run all specs and features"
-  def all
-    exit(units_command && acceptance_command)
-  end
-
-  desc "ci", "Run tests on Travis"
-  def ci
-    ENV["CI"] = "true" # Travis-CI also sets this, but set it here for local testing
-    all
-  end
-
-  desc "unit", "Run unit tests"
-  def unit
-    exit(units_command)
-  end
-
-  desc "acceptance", "Run acceptance tests"
-  def acceptance
-    exit(acceptance_command)
-  end
-
-  no_tasks do
-    def units_command
-      run("rspec --color spec/unit")
-    end
-
-    def acceptance_command
-      run("cucumber --color --tags ~@no_run --strict")
-    end
-  end
-end

data/appveyor.yml

@@ -1,31 +0,0 @@
-version: "master-{build}"
-
-os: Windows Server 2012 R2
-platform:
-  - x64
-
-clone_depth: 1
-skip_tags: true
-skip_branch_with_pr: true
-branches:
-  only:
-    - master
-
-# caching vendor/bundle appears to break horribly in the face of gems checked out of git
-# cache:
-#   - vendor/bundle
-
-install:
-  - ps: iex (irm https://omnitruck.chef.io/install.ps1); Install-Project -Project chefdk -channel stable
-  - bundle config --local path vendor/bundle
-  - SET CI=true
-  - SET BUNDLE_WITHOUT=changelog:style
-
-build_script:
-  - ps: c:\opscode\chefdk\bin\chef.bat shell-init powershell | iex
-  - bundle install || bundle install || bundle install
-
-test_script:
-  - SET SPEC_OPTS=--format progress
-  - c:\opscode\chefdk\bin\chef.bat exec bundle exec rake spec
-  - c:\opscode\chefdk\bin\chef.bat exec bundle exec cucumber --tags ~@not-windows

data/docs/berkshelf_for_newcomers.md

@@ -1,64 +0,0 @@
-# Berkshelf for Newcomers
-
-Berkshelf is a tool to help manage cookbook dependencies.  If your cookbook depends on other cookbooks, Berkshelf lets you do the following:
-
-* download all cookbooks you depend on to your local machine for development and testing using `berks install`
-* upload your cookbook and all dependencies to your Chef server using `berks upload`
-* update your dependencies using `berks update`
-
-The above are the main Berkshelf commands that will comprise the bulk of your workflow.
-
-Berkshelf is included in the ChefDK (at least at v.0.10.0), and `chef generate cookbook` will set up your cookbook with the necessary files for Berkshelf usage.
-
-## A quick example
-
-Suppose you have a cookbook with the following `metadata.rb`:
-
-```
-name 'example_cookbook'
-description 'Installs/Configures example_cookbook'
-long_description 'Installs/Configures example_cookbook'
-version '0.1.0'
-
-depends 'apt', '~> 2.3'
-```
-
-To work on this cookbook locally, you need to download an `apt` cookbook matching the constraints.  Berkshelf handles this for you:
-
-```
-$ berks install
-Resolving cookbook dependencies...
-Fetching 'example_cookbook' from source at .
-Fetching cookbook index from https://supermarket.chef.io...
-Using example_cookbook (0.1.0) from source at .
-Using apt (2.9.2)
-```
-
-When done your work, you need to push both your cookbook and the apt cookbook up to your Chef server.  With Berkshelf:
-
-```
-$ berks upload
-Uploaded apt (2.9.2) to: 'https://your_chef_server_url'
-Uploaded example_cookbook (0.1.0) to: 'your_chef_server_url'
-```
-
-The above is a trivial example.  If your cookbook has several dependencies, which in turn have dependencies, Berkshelf handles it all automatically, significantly improving your workflow.
-
-## What's in the background
-
-* the cookbook's `metadata.rb` specifies the cookbook dependencies and required versions
-* the [Berksfile](https://docs.chef.io/berkshelf.html#the-berksfile) in your cookbook's root directory tells Berkshelf where to find cookbooks.  You can have multiple sources, or can pull individual cookbooks from specific locations, such as your own Supermarket, GitHub, or a file server.
-* `berks install` downloads cookbooks and their dependencies to the [Berkshelf](https://docs.chef.io/berkshelf.html#berkshelf-cli), a place on your local disk.
-* a Berksfile.lock is generated on `berks install` which specifies the exact cookbook versions that were used at that point
-
-## Cookbook versioning
-
-Berkshelf relies on cookbook versioning to work correctly.  A cookbook's version is tracked in its `metadata.rb`, and should follow the guidelines outlined at http://semver.org/.
-
-# Further reading
-
-* https://docs.chef.io/berkshelf.html
-
---
-
-Good luck with Berkshelf!

data/features/artifactory.feature

@@ -1,70 +0,0 @@
-Feature: Installing cookbooks from an Artifactory server
-  This integration test uses some environment variables to configure which
-  Artifactory server to talk to, as there is no ArtifactoryZero to test against.
-  If those aren't present, we skip the tests.
-
-  $TEST_BERKSHELF_ARTIFACTORY - URL to the Chef virtual repository.
-  $TEST_BERKSHELF_ARTIFACTORY_API_KEY - API key to use.
-
-  Scenario: when the cookbook exists
-    Given I have a Berksfile pointing at an authenticated Artifactory server with:
-      """
-      cookbook 'poise', '2.7.2'
-      """
-    When I successfully run `berks install`
-    Then the output should contain:
-      """
-      Installing poise (2.7.2)
-      """
-    And the cookbook store should have the cookbooks:
-      | poise | 2.7.2 |
-
-  Scenario: when the cookbook does not exist
-    Given I have a Berksfile pointing at an authenticated Artifactory server with:
-      """
-      cookbook '1234567890'
-      """
-    When I run `berks install`
-    Then the output should contain:
-      """
-      Unable to find a solution for demands: 1234567890 (>= 0.0.0)
-      """
-    And the exit status should be "NoSolutionError"
-
-  Scenario: when the cookbook exists, but the version does not
-    Given I have a Berksfile pointing at an authenticated Artifactory server with:
-      """
-      cookbook 'poise', '0.0.0'
-      """
-    When I run `berks install`
-    Then the output should contain:
-      """
-      Unable to find a solution for demands: poise (= 0.0.0)
-      """
-    And the exit status should be "NoSolutionError"
-
-  Scenario: when the API key is not present:
-    Given I have a Berksfile pointing at an Artifactory server with:
-      """
-      cookbook 'poise'
-      """
-    When I run `berks install`
-    Then the output should contain:
-      """
-      Unable to find a solution for demands: poise (>= 0.0.0)
-      """
-    And the exit status should be "NoSolutionError"
-
-  Scenario: when the API key is given in $ARTIFACTORY_API_KEY:
-    Given I have a Berksfile pointing at an Artifactory server with:
-      """
-      cookbook 'poise', '2.7.2'
-      """
-    And the environment variable ARTIFACTORY_API_KEY is $TEST_BERKSHELF_ARTIFACTORY_API_KEY
-    When I successfully run `berks install`
-    Then the output should contain:
-      """
-      Installing poise (2.7.2)
-      """
-    And the cookbook store should have the cookbooks:
-      | poise | 2.7.2 |

data/features/berksfile.feature

@@ -1,46 +0,0 @@
-Feature: Evaluating a Berksfile
-  Scenario: Containing pure Ruby
-    Given I write to "Berksfile" with:
-      """
-      source 'https://supermarket.chef.io'
-
-      if ENV['BACON']
-        puts "If you don't got bacon..."
-      else
-        puts "No bacon :'("
-      end
-      """
-    And the environment variable BACON is "1"
-    When I successfully run `berks install`
-    Then the output should contain:
-      """
-      If you don't got bacon...
-      """
-
-  Scenario: Containing methods I shouldn't be able to call
-    Given I write to "Berksfile" with:
-      """
-      add_location(:foo)
-      """
-    When I run `berks install`
-    Then the output should contain:
-      """
-      An error occurred while reading the Berksfile:
-
-        undefined method `add_location' for
-      """
-    And the exit status should be "BerksfileReadError"
-
-  Scenario: Containing Ruby syntax errors
-    Given I write to "Berksfile" with:
-      """
-      ptus "This is a ruby syntax error"
-      """
-    When I run `berks install`
-    Then the output should contain:
-      """
-      An error occurred while reading the Berksfile:
-
-        undefined method `ptus' for
-      """
-    And the exit status should be "BerksfileReadError"

data/features/commands/apply.feature

@@ -1,41 +0,0 @@
-@api_server
-Feature: berks apply
-  Scenario: Locking a cookbook version with dependencies
-    Given the cookbook store contains a cookbook "fake" "1.0.0" with dependencies:
-      | dependency | 2.0.0 |
-    And the cookbook store has the cookbooks:
-      | dependency | 2.0.0 |
-    And the Chef Server has an environment named "my_env"
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      """
-    When I successfully run `berks install`
-    And I successfully run `berks apply my_env`
-    Then the version locks in the "my_env" environment should be:
-      | fake       | = 1.0.0 |
-      | dependency | = 2.0.0 |
-
-  Scenario: Locking cookbook versions to a non-existent Chef Environment
-    Given the Chef Server does not have an environment named "my_env"
-    And the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      """
-    When I successfully run `berks install`
-    And I run `berks apply my_env`
-    Then the output should contain:
-      """
-      The environment 'my_env' does not exist
-      """
-    And the exit status should be "EnvironmentNotFound"
-
-  Scenario: Locking an environment when no lockfile is present
-    When I run `berks apply my_env`
-    Then the output should contain:
-      """
-      Lockfile not found! Run `berks install` to create the lockfile.
-      """
-    And the exit status should be "LockfileNotFound"

data/features/commands/contingent.feature

@@ -1,47 +0,0 @@
-Feature: berks contingent
-  Background:
-    * the Chef Server is empty
-    * the cookbook store is empty
-
-  Scenario: When there are dependent cookbooks
-    Given the cookbook store has the cookbooks:
-      | dep | 1.0.0 |
-    And the cookbook store contains a cookbook "fake" "1.0.0" with dependencies:
-      | dep | ~> 1.0.0 |
-    And the cookbook store contains a cookbook "ekaf" "1.0.0" with dependencies:
-      | dep | ~> 1.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      cookbook 'ekaf', '1.0.0'
-      """
-    And I run `berks install`
-    And I successfully run `berks contingent dep`
-    Then the output should contain:
-      """
-      Cookbooks in this Berksfile contingent upon 'dep':
-        * ekaf (1.0.0)
-        * fake (1.0.0)
-      """
-
-  Scenario: When there are no dependent cookbooks
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      """
-    And I run `berks install`
-    And I successfully run `berks contingent dep`
-    Then the output should contain:
-      """
-      There are no cookbooks in this Berksfile contingent upon 'dep'.
-      """
-
-  Scenario: When the cookbook is not in the Berksfile
-    Given I have a Berksfile pointing at the local Berkshelf API
-    And I successfully run `berks contingent dep`
-    Then the output should contain:
-      """
-      There are no cookbooks in this Berksfile contingent upon 'dep'.
-      """

data/features/commands/info.feature

@@ -1,141 +0,0 @@
- Feature: berks info
-    Scenario: With no options
-      Given the cookbook store has the cookbooks:
-        | fake | 1.0.0 |
-      And I have a Berksfile pointing at the local Berkshelf API with:
-        """
-        cookbook 'fake', '1.0.0'
-        """
-      And I write to "Berksfile.lock" with:
-        """
-        DEPENDENCIES
-          fake (= 1.0.0)
-
-        GRAPH
-          fake (1.0.0)
-        """
-      When I successfully run `berks info fake`
-      Then the output should contain:
-        """
-                Name: fake
-             Version: 1.0.0
-             License: All rights reserved
-        """
-
-    Scenario: When the parameter is a transitive dependency
-      Given the cookbook store has the cookbooks:
-        | dep | 1.0.0 |
-      And the cookbook store contains a cookbook "fake" "1.0.0" with dependencies:
-        | dep | ~> 1.0.0 |
-      And I have a Berksfile pointing at the local Berkshelf API with:
-        """
-        cookbook 'fake', '1.0.0'
-        """
-      And I write to "Berksfile.lock" with:
-        """
-        DEPENDENCIES
-          fake (= 1.0.0)
-
-        GRAPH
-          dep (1.0.0)
-          fake (1.0.0)
-            dep (~> 1.0.0)
-        """
-      And I successfully run `berks install`
-      When I successfully run `berks info dep`
-      Then the output should contain:
-        """
-                Name: dep
-             Version: 1.0.0
-             License: All rights reserved
-        """
-
-    Scenario: When the cookbook is not in the Berksfile
-      Given I have a Berksfile pointing at the local Berkshelf API
-      When I run `berks info fake`
-      Then the output should contain:
-        """
-        Dependency 'fake' was not found. Please make sure it is in your Berksfile, and then run `berks install` to download and install the missing dependencies.
-        """
-      And the exit status should be "DependencyNotFound"
-
-    Scenario: When there is no lockfile present
-      And I have a Berksfile pointing at the local Berkshelf API with:
-        """
-        cookbook 'fake', '1.0.0'
-        """
-      When I run `berks info fake`
-      Then the output should contain:
-        """
-        Dependency 'fake' was not found. Please make sure it is in your Berksfile, and then run `berks install` to download and install the missing dependencies.
-        """
-      And the exit status should be "DependencyNotFound"
-
-    Scenario: When the cookbook is not installed
-      Given the cookbook store is empty
-      And I have a Berksfile pointing at the local Berkshelf API with:
-        """
-        cookbook 'fake', '1.0.0'
-        """
-      And I write to "Berksfile.lock" with:
-        """
-        DEPENDENCIES
-          fake (= 1.0.0)
-
-        GRAPH
-          fake (1.0.0)
-        """
-      When I run `berks info fake`
-      Then the output should contain:
-        """
-        Cookbook 'fake' (1.0.0) not found in the cookbook store!
-        """
-      And the exit status should be "CookbookNotFound"
-
-Scenario: When the cookbook is a vendored cookbook
-      Given the cookbook store has the cookbooks:
-        | fake | 1.0.0 |
-      And I have a Berksfile pointing at the local Berkshelf API with:
-        """
-        cookbook 'fake', '1.0.0'
-        """
-      And I write to "Berksfile.lock" with:
-        """
-        DEPENDENCIES
-          fake (= 1.0.0)
-
-        GRAPH
-          fake (1.0.0)
-        """
-      And the cookbook store cookbook "fake" "1.0.0" is vendored without a metadata.rb
-      When I successfully run `berks info fake`
-      Then the output should contain:
-        """
-                Name: fake
-             Version: 1.0.0
-             License: All rights reserved
-        """
-
-Scenario: When the cookbook is a vendored cookbook
-      Given the cookbook store has the cookbooks:
-        | fake | 1.0.0 |
-      And I have a Berksfile pointing at the local Berkshelf API with:
-        """
-        cookbook 'fake', '1.0.0'
-        """
-      And I write to "Berksfile.lock" with:
-        """
-        DEPENDENCIES
-          fake (= 1.0.0)
-
-        GRAPH
-          fake (1.0.0)
-        """
-      And the cookbook store cookbook "fake" "1.0.0" is vendored with a metadata.rb
-      When I successfully run `berks info fake`
-      Then the output should contain:
-        """
-                Name: fake
-             Version: 1.0.0
-             License: All rights reserved
-        """