berkshelf 7.0.7 → 7.2.0

data/features/commands/vendor.feature

@@ -1,154 +0,0 @@
-Feature: Vendoring cookbooks to a directory
-  Background:
-    * the Chef Server has cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.0.0 |
-
-  Scenario: successfully vendoring a Berksfile with multiple cookbook demands
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake'
-      cookbook 'ekaf'
-      """
-    When I successfully run `berks vendor cukebooks`
-    Then the directory "cukebooks/fake" should contain version "1.0.0" of the "fake" cookbook
-    And the directory "cukebooks/ekaf" should contain version "2.0.0" of the "ekaf" cookbook
-
-  Scenario: attempting to vendor when no Berksfile is present
-    When I run `berks vendor cukebooks`
-    Then the exit status should be "BerksfileNotFound"
-
-  Scenario: vendoring a Berksfile with a metadata demand
-    Given a cookbook named "fake"
-    And I cd to "fake"
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      metadata
-      """
-    When I successfully run `berks vendor cukebooks`
-    Then the directory "cukebooks/fake" should contain version "0.0.0" of the "fake" cookbook
-
-  Scenario: vendoring a cookbook with transitive dependencies
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      metadata
-      """
-    And I write to "metadata.rb" with:
-      """
-      name 'bacon'
-      version '1.0.0'
-
-      depends 'fake'
-      depends 'ekaf'
-      """
-    When I successfully run `berks vendor vendor`
-    Then the directory "vendor/bacon" should contain version "1.0.0" of the "bacon" cookbook
-    And the directory "vendor/fake" should contain version "1.0.0" of the "fake" cookbook
-    And the directory "vendor/ekaf" should contain version "2.0.0" of the "ekaf" cookbook
-
-  Scenario: vendoring a cookbook with transitive dependencies when a lockfile is present
-    Given a cookbook named "bacon"
-    And the cookbook "bacon" has the file "metadata.rb" with:
-      """
-      name 'bacon'
-      version '1.0.0'
-
-      depends 'fake'
-      depends 'ekaf'
-      """
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', path: './bacon'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        bacon
-          path: ./bacon
-
-      GRAPH
-        bacon (1.0.0)
-          ekaf (>= 0.0.0)
-          fake (>= 0.0.0)
-        ekaf (2.0.0)
-        fake (1.0.0)
-      """
-    When I successfully run `berks vendor vendor`
-    Then the directory "vendor/bacon" should contain version "1.0.0" of the "bacon" cookbook
-    And the directory "vendor/fake" should contain version "1.0.0" of the "fake" cookbook
-    And the directory "vendor/ekaf" should contain version "2.0.0" of the "ekaf" cookbook
-
-  Scenario: vendoring without an explicit path to vendor into
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake'
-      """
-    When I successfully run `berks vendor`
-    Then the directory "berks-cookbooks/fake" should contain version "1.0.0" of the "fake" cookbook
-
-  Scenario: vendoring to a directory that already exists
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake'
-      """
-    And a directory named "cukebooks"
-    And a directory named "cukebooks/fake/ponies"
-    And a directory named "cukebooks/existing_cookbook"
-    When I successfully run `berks vendor --delete cukebooks`
-    Then the directory "cukebooks/fake" should contain version "1.0.0" of the "fake" cookbook
-    And a directory named "cukebooks/fake/ponies" should not exist
-    And a directory named "cukebooks/existing_cookbook" should not exist
-
-  Scenario: vendoring into a nested directory
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake'
-      """
-    When I successfully run `berks vendor path/to/cukebooks`
-    Then the directory "path/to/cukebooks/fake" should contain version "1.0.0" of the "fake" cookbook
-
-  Scenario: vendoring a cookbook with chefignores
-    Given a cookbook named "bacon"
-    And the cookbook "bacon" has the file "metadata.rb" with:
-      """
-      name 'bacon'
-      version '1.0.0'
-      """
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', path: './bacon'
-      """
-    And the cookbook "bacon" has the file "chefignore" with:
-      """
-      *.turd
-      """
-    And the cookbook "bacon" has the file "foo.turd" with:
-      """
-      poop
-      """
-    And the cookbook "bacon" has the file "recipes/foo.turd" with:
-      """
-      poop
-      """
-    When I successfully run `berks vendor vendor`
-    Then the directory "vendor/bacon" should contain version "1.0.0" of the "bacon" cookbook
-    And a file named "vendor/bacon/foo.turd" should not exist
-    And a file named "vendor/bacon/recipes/foo.turd" should not exist
-
-  Scenario: metadata.json / metadata.rb handling when vendoring a cookbook
-    Given a cookbook named "bacon"
-    And the cookbook "bacon" has the file "metadata.rb" with:
-      """
-      name 'bacon'
-      version '1.0.0'
-      """
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', path: './bacon'
-      """
-    When I successfully run `berks vendor vendor`
-    Then the directory "vendor/bacon" should contain version "1.0.0" of the "bacon" cookbook
-    And a file named "vendor/bacon/metadata.json" should exist
-    And a file named "vendor/bacon/metadata.rb" should exist
-    And a file named "bacon/metadata.rb" should exist
-    And a file named "bacon/metadata.json" should not exist

data/features/commands/verify.feature

@@ -1,29 +0,0 @@
-Feature: berks verify
-  Scenario: running verify when there is no Lockfile present
-    Given a cookbook named "sparkle_motion"
-    And I cd to "sparkle_motion"
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      metadata
-      """
-    And I run `berks verify`
-    Then the output should contain:
-      """
-      Lockfile not found! Run `berks install` to create the lockfile.
-      """
-    And the exit status should be "LockfileNotFound"
-
-  Scenario: running verify when there is a valid Lockfile present
-    Given a cookbook named "sparkle_motion"
-    And I cd to "sparkle_motion"
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      metadata
-      """
-    When I successfully run `berks install`
-    And I successfully run `berks verify`
-    Then the output should contain:
-      """
-      Verifying (1) cookbook(s)...
-      Verified.
-      """

data/features/commands/viz.feature

@@ -1,66 +0,0 @@
-@graphviz @not-windows
-Feature: berks viz
-  Scenario: With no options
-    * I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      """
-    * I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake (= 1.0.0)
-
-      GRAPH
-        fake (1.0.0)
-      """
-    * I successfully run `berks viz`
-    * a file named "graph.png" should exist
-
-  Scenario: When there are transitive dependencies
-    * I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      """
-    * I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake (= 1.0.0)
-
-      GRAPH
-        dep (1.0.0)
-        fake (1.0.0)
-          dep (~> 1.0.0)
-      """
-    * I successfully run `berks viz`
-    * a file named "graph.png" should exist
-
-  Scenario: When a custom output is given
-    * I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      """
-    * I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake (= 1.0.0)
-
-      GRAPH
-        dep (1.0.0)
-        fake (1.0.0)
-          dep (~> 1.0.0)
-      """
-    * I successfully run `berks viz --outfile ponies.png`
-    * a file named "graph.png" should not exist
-    * a file named "ponies.png" should exist
-
-  Scenario: When there is no lockfile present
-    * I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      """
-    * I run `berks viz`
-    * the output should contain:
-      """
-      Lockfile not found! Run `berks install` to create the lockfile.
-      """
-    * the exit status should be "LockfileNotFound"

data/features/community_site.feature

@@ -1,37 +0,0 @@
-Feature: Installing cookbooks from the community site
-  Scenario: when the cookbook exists
-    Given I have a Berksfile pointing at the community API endpoint with:
-      """
-      cookbook 'apache2', '1.6.6'
-      """
-    When I successfully run `berks install`
-    Then the output should contain:
-      """
-      Installing apache2 (1.6.6)
-      """
-    And the cookbook store should have the cookbooks:
-      | apache2 | 1.6.6 |
-
-  Scenario: when the cookbook does not exist
-    Given I have a Berksfile pointing at the community API endpoint 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 the community API endpoint with:
-      """
-      cookbook 'apache2', '0.0.0'
-      """
-    When I run `berks install`
-    Then the output should contain:
-      """
-      Unable to find a solution for demands: apache2 (= 0.0.0)
-      """
-    And the exit status should be "NoSolutionError"

data/features/help.feature

@@ -1,11 +0,0 @@
-Feature: Appending -h or --help to a command
-  Scenario Outline: Using various help switches
-    Then the output from `<actual>` should be the same as `<expected>`
-    Examples:
-      | actual                | expected |
-      | berks --help          | berks help |
-      | berks -h              | berks help |
-      | berks cookbook --help | berks help cookbook |
-      | berks cookbook -h     | berks help cookbook |
-      | berks shelf --help    | berks shelf help |
-      | berks shelf -h        | berks shelf help |

data/features/json_formatter.feature

@@ -1,158 +0,0 @@
-Feature: --format json
-  Background:
-    * the Chef Server is empty
-    * the cookbook store is empty
-
-  Scenario: JSON output installing a cookbook from the default location
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'berkshelf', '1.0.0'
-      """
-    And the Chef Server has cookbooks:
-      | berkshelf | 1.0.0 |
-    When I successfully run `berks install --format json`
-    Then the output should contain JSON:
-      """
-      {
-        "cookbooks": [
-          {
-            "api_source": "http://127.0.0.1:26310",
-            "location_path": "http://127.0.0.1:26310/cookbooks/berkshelf/1.0.0",
-            "version": "1.0.0",
-            "name": "berkshelf"
-          }
-        ],
-        "errors": [],
-        "messages": [
-          "Resolving cookbook dependencies...",
-          "Fetching cookbook index from http://127.0.0.1:26310..."
-        ],
-        "warnings": []
-      }
-      """
-
-  Scenario: JSON output installing a cookbook we already have
-    Given the cookbook store has the cookbooks:
-      | berkshelf-cookbook-fixture | 1.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'berkshelf-cookbook-fixture', '1.0.0'
-      """
-    When I successfully run `berks install --format json`
-    Then the output should contain JSON:
-      """
-      {
-        "cookbooks": [
-          {
-            "name": "berkshelf-cookbook-fixture",
-            "version": "1.0.0"
-          }
-        ],
-        "errors": [],
-        "messages": [
-          "Resolving cookbook dependencies...",
-          "Fetching cookbook index from http://127.0.0.1:26310..."
-        ],
-        "warnings": []
-      }
-      """
-
-  Scenario: JSON output when running the show command
-    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 show fake --format json`
-    Then the output should contain JSON:
-      """
-      {
-        "cookbooks": [
-          {
-            "name": "fake",
-            "path": "<%= Berkshelf.cookbook_store.storage_path.join('fake-1.0.0') %>"
-          }
-        ],
-        "errors": [],
-        "messages": [],
-        "warnings": []
-      }
-      """
-
-  Scenario: JSON output when running the upload command
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'example_cookbook', path: '../../spec/fixtures/cookbooks/example_cookbook-0.5.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        example_cookbook
-          path: ../../spec/fixtures/cookbooks/example_cookbook-0.5.0
-
-      GRAPH
-        example_cookbook (0.5.0)
-      """
-    When I successfully run `berks upload --format json`
-    Then the output should contain JSON:
-      """
-      {
-        "cookbooks": [
-          {
-            "name": "example_cookbook",
-            "version": "0.5.0",
-            "uploaded_to": "http://localhost:26310"
-          }
-        ],
-        "errors": [],
-        "messages": [],
-        "warnings": []
-      }
-      """
-
-  Scenario: JSON output when running the outdated command
-    Given the cookbook store has the cookbooks:
-      | seth | 0.1.0 |
-    And the Chef Server has cookbooks:
-      | seth | 0.1.0 |
-      | seth | 0.2.9 |
-      | seth | 1.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'seth', '~> 0.1'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        seth (~> 0.1)
-
-      GRAPH
-        seth (0.1.0)
-      """
-    And I successfully run `berks outdated --format json`
-    Then the output should contain JSON:
-      """
-      {
-        "cookbooks": [
-          {
-            "local": "0.1.0",
-            "remote": {
-              "http://127.0.0.1:26310": "0.2.9"
-            },
-            "name": "seth"
-          }
-        ],
-        "errors": [],
-        "messages": [],
-        "warnings": []
-      }
-      """