RubyGems - berkshelf - Versions diffs - 7.0.7 → 7.0.8 - Mend

berkshelf 7.0.7 → 7.0.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (63) hide show

checksums.yaml +4 -4
data/Rakefile +1 -1
data/berkshelf.gemspec +8 -9
data/bin/berks +5 -0
data/lib/berkshelf/cached_cookbook.rb +1 -1
data/lib/berkshelf/chef_config_compat.rb +1 -0
data/lib/berkshelf/chef_repo_universe.rb +2 -2
data/lib/berkshelf/formatters/json.rb +3 -3
data/lib/berkshelf/lockfile.rb +3 -3
data/lib/berkshelf/uploader.rb +3 -3
data/lib/berkshelf/version.rb +1 -1
metadata +32 -186
data/.github/lock.yml +0 -1
data/.gitignore +0 -30
data/.rubocop.yml +0 -12
data/.travis.yml +0 -73
data/CHANGELOG.legacy.md +0 -307
data/CHANGELOG.md +0 -1589
data/CONTRIBUTING.md +0 -68
data/Gemfile.lock +0 -292
data/PLUGINS.md +0 -25
data/README.md +0 -72
data/Thorfile +0 -61
data/appveyor.yml +0 -31
data/docs/berkshelf_for_newcomers.md +0 -64
data/features/artifactory.feature +0 -70
data/features/berksfile.feature +0 -46
data/features/commands/apply.feature +0 -41
data/features/commands/contingent.feature +0 -47
data/features/commands/info.feature +0 -141
data/features/commands/install.feature +0 -646
data/features/commands/list.feature +0 -78
data/features/commands/outdated.feature +0 -176
data/features/commands/package.feature +0 -17
data/features/commands/search.feature +0 -17
data/features/commands/shelf/list.feature +0 -32
data/features/commands/shelf/show.feature +0 -113
data/features/commands/shelf/uninstall.feature +0 -96
data/features/commands/show.feature +0 -83
data/features/commands/update.feature +0 -142
data/features/commands/upload.feature +0 -499
data/features/commands/vendor.feature +0 -154
data/features/commands/verify.feature +0 -29
data/features/commands/viz.feature +0 -66
data/features/community_site.feature +0 -37
data/features/help.feature +0 -11
data/features/json_formatter.feature +0 -158
data/features/lifecycle.feature +0 -378
data/features/lockfile.feature +0 -378
data/features/step_definitions/berksfile_steps.rb +0 -54
data/features/step_definitions/chef/config_steps.rb +0 -12
data/features/step_definitions/chef_server_steps.rb +0 -60
data/features/step_definitions/cli_steps.rb +0 -18
data/features/step_definitions/config_steps.rb +0 -46
data/features/step_definitions/environment_steps.rb +0 -11
data/features/step_definitions/filesystem_steps.rb +0 -286
data/features/step_definitions/gem_steps.rb +0 -13
data/features/step_definitions/json_steps.rb +0 -29
data/features/step_definitions/utility_steps.rb +0 -11
data/features/support/aruba.rb +0 -12
data/features/support/env.rb +0 -77
data/spec/fixtures/cookbooks/example_cookbook/.gitignore +0 -2
data/spec/fixtures/cookbooks/example_cookbook/.kitchen.yml +0 -26

data/features/commands/list.feature DELETED

@@ -1,78 +0,0 @@
-Feature: berks list
-  Scenario: When everything is good
-    Given the cookbook store has the cookbooks:
-      | fake1 | 1.0.0 |
-      | fake2 | 1.0.1 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake1', '1.0.0'
-      cookbook 'fake2', '1.0.1'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        fake1 (= 1.0.0)
-        fake2 (= 1.0.1)
-      GRAPH
-        fake1 (1.0.0)
-        fake2 (1.0.1)
-      """
-    When I successfully run `berks list`
-    Then the output should contain:
-      """
-      Cookbooks installed by your Berksfile:
-        * fake1 (1.0.0)
-        * fake2 (1.0.1)
-      """
-  Scenario: When the lockfile is not present
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '1.0.0'
-      """
-    When I run `berks list`
-    Then the output should contain:
-      """
-      Lockfile not found! Run `berks install` to create the lockfile.
-      """
-    And the exit status should be "LockfileNotFound"
-  Scenario: When a dependency is not in the lockfile
-    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
-      GRAPH
-        not_fake (1.0.0)
-      """
-    When I run `berks list`
-    Then the output should contain:
-      """
-      The lockfile is out of sync! Run `berks install` to sync the lockfile.
-      """
-    And the exit status should be "LockfileOutOfSync"
-  Scenario: When a dependency is not installed
-    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 run `berks list`
-    Then the output should contain:
-      """
-      The cookbook 'fake (1.0.0)' is not installed. Please run `berks install` to download and install the missing dependency.
-      """
-    And the exit status should be "DependencyNotInstalled"

data/features/commands/outdated.feature DELETED

@@ -1,176 +0,0 @@
-Feature: berks outdated
-  Scenario: the dependency is up to date
-    Given the Chef Server has cookbooks:
-      | bacon | 1.0.0 |
-      | bacon | 1.1.0 |
-    And the cookbook store has the cookbooks:
-      | bacon | 1.1.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', '~> 1.1.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        bacon (~> 1.1.0)
-      GRAPH
-        bacon (1.1.0)
-      """
-    When I successfully run `berks outdated`
-    Then the output should contain:
-      """
-      All cookbooks up to date!
-      """
-  Scenario: the dependency has no version constraint and there are new items
-    Given the Chef Server has cookbooks:
-      | bacon | 1.0.0 |
-      | bacon | 1.1.0 |
-    And the cookbook store has the cookbooks:
-      | bacon | 1.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        bacon
-      GRAPH
-        bacon (1.0.0)
-      """
-    When I successfully run `berks outdated`
-    Then the output should contain:
-      """
-      The following cookbooks have newer versions:
-        * bacon (1.0.0 => 1.1.0)
-      """
-  Scenario: the dependency has a version constraint and there are new items that satisfy it
-    Given the Chef Server has cookbooks:
-      | bacon | 1.1.0 |
-      | bacon | 1.2.1 |
-      | bacon | 1.5.8 |
-    And the cookbook store has the cookbooks:
-      | bacon | 1.0.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', '~> 1.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        bacon (~> 1.0)
-      GRAPH
-        bacon (1.0.0)
-      """
-    When I successfully run `berks outdated`
-    Then the output should contain:
-      """
-      The following cookbooks have newer versions:
-        * bacon (1.0.0 => 1.5.8)
-      """
-  Scenario: the dependency has a version constraint and there are new items that don't satisfy it
-    Given the Chef Server has cookbooks:
-      | bacon | 1.1.0 |
-      | bacon | 1.5.8 |
-    And the cookbook store has the cookbooks:
-      | bacon | 1.1.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', '~> 1.1.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        bacon (~> 1.1.0)
-      GRAPH
-        bacon (1.1.0)
-      """
-    When I successfully run `berks outdated`
-    Then the output should contain:
-      """
-      All cookbooks up to date!
-      """
-  Scenario: the dependency has a version constraint and there are new items that satisfy it and --all is given
-    Given the Chef Server has cookbooks:
-      | bacon | 1.1.0 |
-      | bacon | 1.5.8 |
-    And the cookbook store has the cookbooks:
-      | bacon | 1.1.0 |
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', '~> 1.1.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        bacon (~> 1.1.0)
-      GRAPH
-        bacon (1.1.0)
-      """
-    When I successfully run `berks outdated --all`
-    Then the output should contain:
-      """
-      The following cookbooks have newer versions:
-        * bacon (1.1.0 => 1.5.8)
-      """
-  Scenario: When the lockfile is not present
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', '1.0.0'
-      """
-    When I run `berks outdated`
-    Then the output should contain:
-      """
-      Lockfile not found! Run `berks install` to create the lockfile.
-      """
-    And the exit status should be "LockfileNotFound"
-  Scenario: When a dependency is not in the lockfile
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', '1.0.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-      GRAPH
-        not_fake (1.0.0)
-      """
-    When I run `berks outdated`
-    Then the output should contain:
-      """
-      The lockfile is out of sync! Run `berks install` to sync the lockfile.
-      """
-    And the exit status should be "LockfileOutOfSync"
-  Scenario: When a dependency is not installed
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'bacon', '1.0.0'
-      """
-    And I write to "Berksfile.lock" with:
-      """
-      DEPENDENCIES
-        bacon (= 1.0.0)
-      GRAPH
-        bacon (1.0.0)
-      """
-    When I run `berks outdated`
-    Then the output should contain:
-      """
-      The cookbook 'bacon (1.0.0)' is not installed. Please run `berks install` to download and install the missing dependency.
-      """
-    And the exit status should be "DependencyNotInstalled"

data/features/commands/package.feature DELETED

@@ -1,17 +0,0 @@
-@api_server
-Feature: berks package
-  Background:
-    * the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-  Scenario: When no options are passed
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '~> 1.0.0'
-      """
-    When I successfully run `berks package my-cookbooks.tar.gz`
-    Then a file named "my-cookbooks.tar.gz" should exist
-    And the output should contain:
-      """
-      Cookbook(s) packaged to
-      """

data/features/commands/search.feature DELETED

@@ -1,17 +0,0 @@
-Feature: berks search
-  Scenario: Searching for a cookbook by name
-    * I successfully run `berks search berkshelf-cookbook-fixture`
-    * the output should contain:
-      """
-      berkshelf-cookbook-fixture (1.0.0)
-      """
-  Scenario: Searching for a cookbook by partial name
-    * I successfully run `berks search berkshelf-`
-    * the results should have the cookbooks:
-      """
-      berkshelf-api (1.2.2)
-      berkshelf-api-server (2.2.0)
-      berkshelf-cookbook-fixture (1.0.0)
-      """
-    * the results should each start with "berkshelf-"

data/features/commands/shelf/list.feature DELETED

@@ -1,32 +0,0 @@
-Feature: berks shelf list
-  Scenario: With no cookbooks in the store
-    When I successfully run `berks shelf list`
-    Then the output should contain:
-      """
-      There are no cookbooks in the Berkshelf shelf
-      """
-  Scenario: With two cookbooks in the store
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.3.4 |
-    When I successfully run `berks shelf list`
-    Then the output should contain:
-      """
-      Cookbooks in the Berkshelf shelf:
-        * ekaf (2.3.4)
-        * fake (1.0.0)
-      """
-  Scenario: With multiple cookbook versions installed
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | fake | 1.1.0 |
-      | fake | 1.2.0 |
-      | fake | 2.0.0 |
-    When I successfully run `berks shelf list`
-    Then the output should contain:
-      """
-      Cookbooks in the Berkshelf shelf:
-        * fake (1.0.0, 1.1.0, 1.2.0, 2.0.0)
-      """

data/features/commands/shelf/show.feature DELETED

@@ -1,113 +0,0 @@
-Feature: berks shelf show
-  Scenario: With a cookbook that is not in the store
-    When I run `berks shelf show fake`
-    Then the output should contain:
-      """
-      Cookbook 'fake' not found in the Berkshelf shelf!
-      """
-    And the exit status should be "CookbookNotFound"
-  Scenario: With cookbooks in the store
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.3.4 |
-    When I successfully run `berks shelf show fake`
-    Then the output should contain:
-      """
-      Displaying all versions of 'fake' in the Berkshelf shelf:
-              Name: fake
-           Version: 1.0.0
-           License: All rights reserved
-      """
-    And the output should not contain:
-      """
-      Name: ekaf
-      """
-  Scenario: With cookbooks in the store and the --version option
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.3.4 |
-    When I successfully run `berks shelf show fake --version 1.0.0`
-    Then the output should contain:
-      """
-      Displaying 'fake' (1.0.0) in the Berkshelf shelf:
-              Name: fake
-           Version: 1.0.0
-           License: All rights reserved
-      """
-    And the output should not contain:
-      """
-      Name: ekaf
-      """
-  Scenario: With cookbooks in the store and the --version option doesn't exist
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.3.4 |
-    When I run `berks shelf show fake --version 1.2.3`
-    Then the output should contain:
-      """
-      Cookbook 'fake' (1.2.3) not found in the Berkshelf shelf!
-      """
-    And the exit status should be "CookbookNotFound"
-  Scenario: With multiple cookbook versions installed
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | fake | 1.1.0 |
-      | fake | 1.2.0 |
-      | fake | 2.0.0 |
-    When I successfully run `berks shelf show fake`
-    Then the output should contain:
-      """
-      Displaying all versions of 'fake' in the Berkshelf shelf:
-              Name: fake
-           Version: 1.0.0
-           License: All rights reserved
-              Name: fake
-           Version: 1.1.0
-           License: All rights reserved
-              Name: fake
-           Version: 1.2.0
-           License: All rights reserved
-              Name: fake
-           Version: 2.0.0
-           License: All rights reserved
-      """
-  Scenario: With multiple cookbook versions installed and the --version flag
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | fake | 1.1.0 |
-      | fake | 1.2.0 |
-      | fake | 2.0.0 |
-    When I successfully run `berks shelf show fake --version 1.0.0`
-    Then the output should contain:
-      """
-      Displaying 'fake' (1.0.0) in the Berkshelf shelf:
-              Name: fake
-           Version: 1.0.0
-           License: All rights reserved
-      """
-    And the output should not contain:
-      """
-              Name: fake
-           Version: 1.1.0
-           License: All rights reserved
-      """
-    And the output should not contain:
-      """
-              Name: fake
-           Version: 1.2.0
-           License: All rights reserved
-      """
-    And the output should not contain:
-      """
-              Name: fake
-           Version: 2.0.0
-           License: All rights reserved
-      """

data/features/commands/shelf/uninstall.feature DELETED

@@ -1,96 +0,0 @@
-Feature: berks shelf uninstall
-  Scenario: With no cookbooks in the store
-    When I run `berks shelf uninstall fake`
-    Then the output should contain:
-      """
-      Cookbook 'fake' not found in the Berkshelf shelf!
-      """
-    And the exit status should be "CookbookNotFound"
-  Scenario: With two cookbooks in the store
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | ekaf | 2.3.4 |
-    When I successfully run `berks shelf uninstall fake`
-    Then the output should contain:
-      """
-      Successfully uninstalled fake (1.0.0)
-      """
-    And the cookbook store should not have the cookbooks:
-      | fake | 1.0.0 |
-    And the cookbook store should have the cookbooks:
-      | ekaf | 2.3.4 |
-  Scenario: With multiple cookbook versions installed
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | fake | 1.1.0 |
-      | fake | 1.2.0 |
-      | fake | 2.0.0 |
-    When I successfully run `berks shelf uninstall fake`
-    Then the output should contain:
-      """
-      Successfully uninstalled fake (1.0.0)
-      Successfully uninstalled fake (1.1.0)
-      Successfully uninstalled fake (1.2.0)
-      Successfully uninstalled fake (2.0.0)
-      """
-    And the cookbook store should not have the cookbooks:
-      | fake | 1.0.0 |
-      | fake | 1.1.0 |
-      | fake | 1.2.0 |
-      | fake | 2.0.0 |
-  Scenario: When specifying a version
-    Given the cookbook store has the cookbooks:
-      | fake | 1.0.0 |
-      | fake | 1.1.0 |
-      | fake | 1.2.0 |
-      | fake | 2.0.0 |
-    When I successfully run `berks shelf uninstall fake --version 1.0.0`
-    Then the output should contain:
-      """
-      Successfully uninstalled fake (1.0.0)
-      """
-    And the cookbook store should not have the cookbooks:
-      | fake | 1.0.0 |
-    And the cookbook store should have the cookbooks:
-      | fake | 1.1.0 |
-      | fake | 1.2.0 |
-      | fake | 2.0.0 |
-      # FIXME: there seems to be a bug in aruba on windows related to
-      # interactive stuff that i fully don't understand
-  @spawn @not-windows
-  Scenario: With contingencies
-    Given the cookbook store contains a cookbook "fake" "1.0.0" with dependencies:
-      | ekaf | 2.3.4 |
-    And the cookbook store has the cookbooks:
-      | ekaf | 2.3.4 |
-    When I run `berks shelf uninstall ekaf` interactively
-    And I type "yes"
-    Then the output should contain:
-      """
-      [fake (1.0.0)] depend on ekaf.
-      Are you sure you want to continue? (y/N)
-      """
-    And the output should contain:
-      """
-      Successfully uninstalled ekaf (2.3.4)
-      """
-    And the cookbook store should not have the cookbooks:
-      | ekaf | 2.3.4 |
-  Scenario: With contingencies and the --force flag
-    Given the cookbook store contains a cookbook "fake" "1.0.0" with dependencies:
-      | ekaf | 2.3.4 |
-    And the cookbook store has the cookbooks:
-      | ekaf | 2.3.4 |
-    When I run `berks shelf uninstall ekaf --force`
-    Then the output should contain:
-      """
-      Successfully uninstalled ekaf (2.3.4)
-      """
-    And the cookbook store should not have the cookbooks:
-      | ekaf | 2.3.4 |