berkshelf 5.2.0 → 8.0.15

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/config.feature

@@ -1,111 +0,0 @@
-Feature: Reading a Berkshelf configuration file
-  Scenario: Missing a Berkshelf configuration file
-    When I successfully run `berks cookbook sparkle_motion`
-    Then the resulting "sparkle_motion" Vagrantfile should contain:
-      | config.omnibus.chef_version = 'latest' |
-      | config.vm.box = 'bento/ubuntu-14.04' |
-
-  Scenario: Using a Berkshelf configuration file that sets the vagrant-omnibus plugin chef version
-    Given I have a Berkshelf config file containing:
-    """
-    {
-      "vagrant": {
-        "omnibus": {
-          "version": "11.4.4"
-        },
-        "vm": {
-          "box": "bento/ubuntu-14.04",
-          "forward_port": {
-            "12345": "54321"
-          }
-        }
-      }
-    }
-    """
-    When I successfully run `berks cookbook sparkle_motion`
-    Then the resulting "sparkle_motion" Vagrantfile should contain:
-      | config.omnibus.chef_version = '11.4.4' |
-      | config.vm.box = 'bento/ubuntu-14.04' |
-      | config.vm.network :forwarded_port, guest: 12345, host: 54321 |
-      | config.vm.network :private_network, type: 'dhcp' |
-    And the exit status should be 0
-
-  Scenario: Using a Berkshelf configuration file that sets the vagrant-omnibus plugin chef version to latest
-    Given I have a Berkshelf config file containing:
-    """
-    {
-      "vagrant": {
-        "omnibus": {
-          "version": "latest"
-        },
-        "vm": {
-          "box": "bento/ubuntu-14.04",
-          "forward_port": {
-            "12345": "54321"
-          }
-        }
-      }
-    }
-    """
-    When I successfully run `berks cookbook sparkle_motion`
-    Then the resulting "sparkle_motion" Vagrantfile should contain:
-      | config.omnibus.chef_version = 'latest' |
-      | config.vm.box = 'bento/ubuntu-14.04' |
-      | config.vm.network :forwarded_port, guest: 12345, host: 54321 |
-      | config.vm.network :private_network, type: 'dhcp' |
-
-  Scenario: Using a partial Berkshelf configuration file
-    Given I have a Berkshelf config file containing:
-    """
-    {
-      "vagrant": {
-        "vm": {
-          "forward_port": {
-            "12345": "54321"
-          }
-        }
-      }
-    }
-    """
-    When I successfully run `berks cookbook sparkle_motion`
-    Then the resulting "sparkle_motion" Vagrantfile should contain:
-      | config.vm.network :forwarded_port, guest: 12345, host: 54321 |
-
-  Scenario: Using an invalid Berkshelf configuration file
-    Given I have a Berkshelf config file containing:
-    """
-    {
-      "vagrant": {
-        "vm": {
-          "box": 1
-        }
-      }
-    }
-    """
-    When I run `berks cookbook sparkle_motion`
-    Then the output should contain "Invalid configuration"
-    And the output should contain "vagrant.vm.box Expected attribute: 'vagrant.vm.box' to be a type of: 'String'"
-    And the exit status should be "InvalidConfiguration"
-
-  Scenario: Using a Berkshelf configuration file with Chef configuration information
-    Given I have a Berkshelf config file containing:
-    """
-    {
-      "chef": {
-        "chef_server_url": "localhost:4000",
-        "validation_client_name": "my_client-validator",
-        "validation_key_path": "/a/b/c/my_client-validator.pem"
-      },
-      "vagrant": {
-        "vm": {
-          "provision": "chef_client"
-        }
-      }
-    }
-    """
-    When I successfully run `berks cookbook sparkle_motion`
-    Then the resulting "sparkle_motion" Vagrantfile should contain:
-      | config.vm.provision :chef_client                    |
-      | chef.chef_server_url        = 'localhost:4000'      |
-      | chef.validation_client_name = 'my_client-validator' |
-      | chef.validation_key_path    = '/a/b/c/my_client-validator.pem' |

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,161 +0,0 @@
-Feature: --format json
-  Background:
-    * the Berkshelf API server's cache is empty
-    * 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 |
-    And the Berkshelf API server's cache is up to date
-    When I successfully run `berks install --format json`
-    Then the output should contain JSON:
-      """
-      {
-        "cookbooks": [
-          {
-            "api_source": "http://127.0.0.1:26210/",
-            "location_path": "http://localhost:26310/",
-            "version": "1.0.0",
-            "name": "berkshelf"
-          }
-        ],
-        "errors": [],
-        "messages": [
-          "Resolving cookbook dependencies...",
-          "Fetching cookbook index from http://127.0.0.1:26210..."
-        ],
-        "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:26210..."
-        ],
-        "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 the Berkshelf API server's cache is up to date
-    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:26210/": "0.2.9"
-            },
-            "name": "seth"
-          }
-        ],
-        "errors": [],
-        "messages": [],
-        "warnings": []
-      }
-      """