berkshelf 5.2.0 → 8.0.15

data/features/commands/update.feature

@@ -1,142 +0,0 @@
-@api_server
-Feature: berks update
-  Background:
-    * the cookbook store has the cookbooks:
-      | fake | 0.1.0 |
-      | fake | 0.2.0 |
-      | fake | 1.0.0 |
-      | ekaf | 1.0.0 |
-      | ekaf | 1.0.1 |
-
-  Scenario: Without a cookbook specified
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'ekaf', '~> 1.0.0'
-      cookbook 'fake', '~> 0.1'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf (~> 1.0.0)
-        fake (~> 0.1)
-
-      GRAPH
-        ekaf (1.0.0)
-        fake (0.1.0)
-      """
-    When I successfully run `berks update`
-    Then the file "Berksfile.lock" should contain:
-      """
-      DEPENDENCIES
-        ekaf (~> 1.0.0)
-        fake (~> 0.1)
-
-      GRAPH
-        ekaf (1.0.1)
-        fake (0.2.0)
-      """
-
-  Scenario: With a single cookbook specified
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'ekaf', '~> 1.0.0'
-      cookbook 'fake', '~> 0.1'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf (~> 1.0.0)
-        fake (~> 0.1)
-
-      GRAPH
-        ekaf (1.0.0)
-        fake (0.1.0)
-      """
-    When I successfully run `berks update fake`
-    Then the file "Berksfile.lock" should contain:
-      """
-      DEPENDENCIES
-        ekaf (~> 1.0.0)
-        fake (~> 0.1)
-
-      GRAPH
-        ekaf (1.0.0)
-        fake (0.2.0)
-      """
-
-  Scenario: With a transitive dependency specified
-    Given the cookbook store contains a cookbook "seth" "1.0.0" with dependencies:
-      | fake | ~> 0.1 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'seth', '1.0.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        seth (= 1.0.0)
-
-      GRAPH
-        fake (0.1.0)
-        seth (1.0.0)
-          fake (~> 0.1)
-      """
-    When I successfully run `berks update fake`
-    Then the file "Berksfile.lock" should contain:
-      """
-      DEPENDENCIES
-        seth (= 1.0.0)
-
-      GRAPH
-        fake (0.2.0)
-        seth (1.0.0)
-          fake (~> 0.1)
-      """
-
-  Scenario: With a git location
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'berkshelf-cookbook-fixture', git: 'git://github.com/RiotGames/berkshelf-cookbook-fixture'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        berkshelf-cookbook-fixture
-          git: git://github.com/RiotGames/berkshelf-cookbook-fixture
-          revision: 70a527e17d91f01f031204562460ad1c17f972ee
-
-      GRAPH
-        berkshelf-cookbook-fixture (0.2.0)
-      """
-    And I successfully run `berks install`
-    When I successfully run `berks update`
-    Then the file "Berksfile.lock" should contain:
-      """
-      DEPENDENCIES
-        berkshelf-cookbook-fixture
-          git: git://github.com/RiotGames/berkshelf-cookbook-fixture
-          revision: a97b9447cbd41a5fe58eee2026e48ccb503bd3bc
-
-      GRAPH
-        berkshelf-cookbook-fixture (1.0.0)
-      """
-
-  Scenario: With a cookbook that does not exist
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake
-
-      GRAPH
-        fake (0.2.0)
-      """
-    When I run `berks update not_real`
-    Then the output should contain:
-      """
-      Dependency 'not_real' 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"

data/features/commands/upload.feature

@@ -1,426 +0,0 @@
-Feature: berks upload
-  Background:
-    * the Chef Server is empty
-    * the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.0.0 |
-      | oops | 3.0.0 |
-
-  Scenario: multiple cookbooks with no arguments
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      cookbook 'ekaf', '2.0.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake (= 1.0.0)
-        ekaf (= 2.0.0)
-
-      GRAPH
-        fake (1.0.0)
-        ekaf (2.0.0)
-      """
-    When I successfully run `berks upload`
-    Then the Chef Server should have the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.0.0 |
-
-  Scenario: a cookbook with a path location
-    Given a cookbook named "fake"
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', path: './fake'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake
-          path: ./fake
-
-      GRAPH
-        fake (0.0.0)
-      """
-    When I successfully run `berks upload`
-    Then the Chef Server should have the cookbooks:
-      | fake | 0.0.0 |
-
-  Scenario: specifying a single cookbook with dependencies
-    Given the cookbook store contains a cookbook "reset" "3.4.5" with dependencies:
-      | fake | = 1.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake',  '1.0.0'
-      cookbook 'ekaf',  '2.0.0'
-      cookbook 'reset', '3.4.5'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf (= 2.0.0)
-        fake (= 1.0.0)
-        reset (= 3.4.5)
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-        reset (3.4.5)
-          fake (= 1.0.0)
-      """
-    When I successfully run `berks upload reset`
-    Then the Chef Server should have the cookbooks:
-      | reset | 3.4.5 |
-    And the Chef Server should not have the cookbooks:
-      | fake  | 1.0.0 |
-      | ekaf  | 2.0.0 |
-
-  Scenario: specifying a single cookbook that is a transitive dependency
-    Given the cookbook store contains a cookbook "reset" "3.4.5" with dependencies:
-      | fake | 1.0.0 |
-      | ekaf | 2.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'reset', '3.4.5'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        reset (= 3.4.5)
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-        reset (3.4.5)
-          ekaf (= 2.0.0)
-          fake (= 1.0.0)
-      """
-    When I successfully run `berks upload fake`
-    Then the Chef Server should have the cookbooks:
-      | fake  | 1.0.0 |
-
-  Scenario: specifying a dependency not defined in the Berksfile
-    Given I have a Berksfile pointing at the local Berkshelf API
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake (= 1.0.0)
-
-      GRAPH
-        fake (1.0.0)
-      """
-    When I run `berks upload reset`
-    Then the output should contain:
-      """
-      Dependency 'reset' 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: specifying multiple cookbooks to upload
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      cookbook 'ekaf', '2.0.0'
-      cookbook 'oops', '3.0.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf (= 2.0.0)
-        fake (= 1.0.0)
-        oops (= 3.0.0)
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-        oops (3.0.0)
-      """
-    When I successfully run `berks upload fake ekaf`
-    Then the Chef Server should have the cookbooks:
-      | fake |
-      | ekaf |
-    And the Chef Server should not have the cookbooks:
-      | oops |
-
-  Scenario: uploading a filter does not change the lockfile
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', group: :take_me
-      cookbook 'ekaf', group: :not_me
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf
-        fake
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-      """
-    When I run `berks upload --only take_me`
-    Then the file "Berksfile.lock" should contain:
-      """
-      DEPENDENCIES
-        ekaf
-        fake
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-      """
-
-  Scenario: uploading a single groups of demands with the --only flag
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', group: :take_me
-      cookbook 'ekaf', group: :not_me
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf
-        fake
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-      """
-    When I successfully run `berks upload --only take_me`
-    Then the Chef Server should have the cookbooks:
-      | fake | 1.0.0 |
-    And the Chef Server should not have the cookbooks:
-      | ekaf | 2.0.0 |
-
-  Scenario: uploading multiple groups of demands with the --only flag
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', group: :take_me
-      cookbook 'ekaf', group: :not_me
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf
-        fake
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-      """
-    When I successfully run `berks upload --only take_me not_me`
-    And the Chef Server should have the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.0.0 |
-
-  Scenario: skipping a single group to upload with the --except flag
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', group: :take_me
-      cookbook 'ekaf', group: :not_me
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf
-        fake
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-      """
-    When I successfully run `berks upload --except not_me`
-    And the Chef Server should have the cookbooks:
-      | fake | 1.0.0 |
-    And the Chef Server should not have the cookbooks:
-      | ekaf | 2.0.0 |
-
-  Scenario: skipping multiple groups with the --except flag
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', group: :take_me
-      cookbook 'ekaf', group: :not_me
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        ekaf
-        fake
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-      """
-    When I successfully run `berks upload --except take_me not_me`
-    And the Chef Server should not have the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.0.0 |
-
-  Scenario: specifying cookbooks with transitive dependencies in a group
-    Given the cookbook store contains a cookbook "reset" "3.4.5" with dependencies:
-      | fake | 1.0.0 |
-    And the cookbook store contains a cookbook "fake" "1.0.0" with dependencies:
-      | ekaf | 2.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      group :rockstars do
-        cookbook 'reset', '3.4.5'
-      end
-
-      group :losers do
-        cookbook 'seth', '1.0.0'
-      end
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        reset (= 3.4.5)
-
-      GRAPH
-        ekaf (2.0.0)
-        fake (1.0.0)
-          ekaf (= 2.0.0)
-        reset (3.4.5)
-          fake (= 1.0.0)
-      """
-    When I successfully run `berks upload --only rockstars`
-    Then the Chef Server should have the cookbooks:
-      | reset | 3.4.5 |
-      | fake  | 1.0.0 |
-      | ekaf  | 2.0.0 |
-    And the Chef Server should not have the cookbooks:
-      | seth | 1.0.0 |
-
-  Scenario: attempting to upload an invalid cookbook
-    Given a cookbook named "cookbook with spaces"
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'cookbook with spaces', path: './cookbook with spaces'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        cookbook with spaces
-          path: ./cookbook with spaces
-
-      GRAPH
-        cookbook with spaces (0.0.0)
-      """
-    When I run `berks upload`
-    Then the output should contain:
-      """
-      The cookbook 'cookbook with spaces' has invalid filenames:
-      """
-    And the exit status should be "InvalidCookbookFiles"
-
-  Scenario: With unicode characters
-    Given a cookbook named "fake"
-    And I cd to "fake"
-    And I write to "README.md" with:
-      """
-      Jamié Wiñsor
-      赛斯瓦戈
-      Μιψηαελ Ιωευ
-      جوستين كامبل
-      """
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      metadata
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake
-          path: .
-          metadata: true
-
-      GRAPH
-        fake (0.0.0)
-      """
-    When I successfully run `berks upload fake`
-    Then the output should contain:
-      """
-      Uploaded fake (0.0.0)
-      """
-
-  Scenario: When the cookbook already exist
-    And the Chef Server has frozen cookbooks:
-      | fake  | 1.0.0 |
-    Given 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 upload`
-    Then the output should contain:
-      """
-      Skipping fake (1.0.0) (frozen)
-      """
-
-  Scenario: When the cookbook already exist and is a metadata location
-    Given a cookbook named "fake"
-    And the cookbook "fake" has the file "Berksfile" with:
-      """
-      metadata
-      """
-    And I cd to "fake"
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake
-          path: .
-          metadata: true
-
-      GRAPH
-        fake (0.0.0)
-      """
-    And the Chef Server has frozen cookbooks:
-      | fake | 0.0.0 |
-    When I successfully run `berks upload`
-    Then the output should contain:
-      """
-      Skipping fake (0.0.0) (frozen)
-      """
-
-  Scenario: When the syntax check is skipped
-    Given a cookbook named "fake"
-    And the cookbook "fake" has the file "recipes/default.rb" with:
-      """
-      Totally not valid Ruby syntax
-      """
-    And the cookbook "fake" has the file "templates/default/file.erb" with:
-      """
-      <% for %>
-      """
-    And the cookbook "fake" has the file "recipes/template.rb" with:
-      """
-      template "/tmp/wadus" do
-        source "file.erb"
-      end
-      """
-    And the cookbook "fake" has the file "Berksfile" with:
-      """
-      source 'https://supermarket.chef.io'
-      metadata
-      """
-    And the cookbook "fake" has the file "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake
-          path: .
-          metadata: true
-
-      GRAPH
-        fake (0.0.0)
-      """
-    And I cd to "fake"
-    When I successfully run `berks upload --skip-syntax-check`
-    Then the Chef Server should have the cookbooks:
-      | fake | 0.0.0 |

data/features/commands/vendor.feature

@@ -1,111 +0,0 @@
-Feature: Vendoring cookbooks to a directory
-  Background:
-    * the Berkshelf API server's cache is empty
-    * the Chef Server has cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.0.0 |
-    * the Berkshelf API server's cache is up to date
-
-  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
-

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.
-      """