berkshelf 5.2.0 → 8.0.15

data/docs/berkshelf_for_newcomers.md

@@ -1,65 +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](http://berkshelf.com/v2.0/#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](http://berkshelf.com/v2.0/#the-berkshelf), 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
-
-* The project homepage, http://http://berkshelf.com/v2.0/
-* https://sethvargo.com/berkshelf-workflow/
-
---
-
-Good luck with Berkshelf!

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,48 +0,0 @@
-Feature: berks contingent
-  Background:
-    * the Berkshelf API server's cache is empty
-    * 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/cookbook.feature

@@ -1,35 +0,0 @@
-Feature: berks cookbook
-  Scenario: With the default options
-    When I successfully run `berks cookbook sparkle_motion`
-    Then I should have a new cookbook skeleton "sparkle_motion"
-
-  Scenario Outline: With various options
-    When I successfully run `berks cookbook sparkle_motion --<option>`
-    Then I should have a new cookbook skeleton "sparkle_motion" with <feature> support
-  Examples:
-    | option            | feature         |
-    | foodcritic        | Foodcritic      |
-    | chef-minitest     | Chef-Minitest   |
-    | scmversion        | SCMVersion      |
-    | no-bundler        | no Bundler      |
-    # Disable testing of skip git until Test Kitchen supports the skip_git flag in its generator
-    # https://github.com/opscode/test-kitchen/issues/141
-    # | skip-git          | no Git          |
-    | skip-vagrant      | no Vagrant      |
-    | skip-test-kitchen | no Test Kitchen |
-
-  Scenario Outline: When a required supporting gem is not installed
-    Given the gem "<gem>" is not installed
-    When I successfully run `berks cookbook sparkle_motion --<option>`
-    Then I should have a new cookbook skeleton "sparkle_motion" with <feature> support
-    And the output should contain a warning to suggest supporting the option "<option>" by installing "<gem>"
-  Examples:
-    | option     | feature    | gem             |
-    | foodcritic | Foodcritic | foodcritic      |
-    | scmversion | SCMVersion | thor-scmversion |
-
-  Scenario: When bundler is not installed
-    Given the gem "bundler" is not installed
-    When I successfully run `berks cookbook sparkle_motion`
-    Then I should have a new cookbook skeleton "sparkle_motion"
-    And the output should contain a warning to suggest supporting the default for "bundler" by installing "bundler"

data/features/commands/info.feature

@@ -1,99 +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
-         Description: A fabulous new cookbook
-              Author: YOUR_COMPANY_NAME
-               Email: YOUR_EMAIL
-             License: none
-        """
-
-    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
-         Description: A fabulous new cookbook
-              Author: YOUR_COMPANY_NAME
-               Email: YOUR_EMAIL
-             License: none
-        """
-
-    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"

data/features/commands/init.feature

@@ -1,27 +0,0 @@
-Feature: berks init
-  Scenario: initializing a path containing a cookbook
-    Given a cookbook named "sparkle_motion"
-    When I successfully run `berks init sparkle_motion`
-    Then the cookbook "sparkle_motion" should have the following files:
-      | Berksfile  |
-      | chefignore |
-    And the file "Berksfile" in the cookbook "sparkle_motion" should contain:
-      """
-      metadata
-      """
-    And the output should contain "Successfully initialized"
-
-  Scenario: initializing a path that does not contain a cookbook
-    Given a directory named "not_a_cookbook"
-    When I run `berks init not_a_cookbook`
-    And the exit status should be "NotACookbook"
-
-  Scenario: initializing with no value given for target
-    Given I write to "metadata.rb" with:
-      """
-      name 'sparkle_motion'
-      """
-    When I successfully run `berks init`
-    Then the output should contain "Successfully initialized"
-    And a file named "Berksfile" should exist
-    And a file named "chefignore" should exist