chef-berksfile-env 1.4.0 → 1.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3f4c0db5a76ae24775f0f45365c8777516b6598f
-  data.tar.gz: 06ac854893dda9d92a30e053fd17d0a3401a208a
+  metadata.gz: 1b9336d11321950aab1d03e24cf3c1d9eb218975
+  data.tar.gz: bb0409c3f4d7276d7424f36b90e18377bf3d75bc
 SHA512:
-  metadata.gz: 1f9a68e6c609813b1e90e3820dc1ecbf0f153eb6ba545853878a2f52922d30cadd5e9ec18f53f208332aa8df9d103d2ac7672f08953b7f99f4379a2c82cb0e50
-  data.tar.gz: 7adf14f6fb70976d17e2f299b396bc2c82fb011d0f810304c66a443ec29f39e254d74eabf4e5530f1b5e5b5a6a6a8a6597d8e8badc972beb4d68c7bf9e3f012b
+  metadata.gz: 84926598e14f3f6ec722f48c1bfd22b531dbdddd89254a7ac09ae9639d84784adf3a6227c2fce10f76529208c49a4645f898fd4338e13bc7ba58618992ce6f6f
+  data.tar.gz: c6e81c0d2b2a0b8ad790be98cc08af75f4d6461fae333ebbbf5022682f0d667bd42bcc302bd06d51877c593ab4839099c86344630fe9481b7384b8f4691f035c

data/README.md

@@ -5,6 +5,8 @@ A Chef plugin which allows you to lock down your Chef Environment's cookbook ver
 
 This is effectively the same as doing `berks apply ...` but via `knife environment from file ...`.
 
+View the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md) to see what has changed.
+
 Installation
 ------------
 
@@ -76,4 +78,4 @@ So why do we do this? Well the only way to use this plugin is if your environmen
     env.instance_eval(IO.read(env_ruby_file))
 
 which means that any context about the location of the environment file is lost. So we have no great way to discern the location of our environment 
-Ruby file, so instead we guess.
+Ruby file, so instead we guess.

data/VERSION

@@ -1 +1 @@
-1.4.0
+1.5.0

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: chef-berksfile-env
 version: !ruby/object:Gem::Version
-  version: 1.4.0
+  version: 1.5.0
 platform: ruby
 authors:
 - Bryan Baugher
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-09-27 00:00:00.000000000 Z
+date: 2018-05-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: berkshelf
@@ -19,7 +19,7 @@ dependencies:
         version: '4.0'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '6.0'
+        version: '8.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -29,27 +29,27 @@ dependencies:
         version: '4.0'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '6.0'
+        version: '8.0'
 - !ruby/object:Gem::Dependency
   name: chef
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '11.0'
+        version: '12.0'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '13.0'
+        version: '15.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '11.0'
+        version: '12.0'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '13.0'
+        version: '15.0'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -95,9 +95,10 @@ dependencies:
 description: "Chef-Berksfile-Env\n==================\n\nA Chef plugin which allows
   you to lock down your Chef Environment's cookbook versions with a Berksfile.\n\nThis
   is effectively the same as doing `berks apply ...` but via `knife environment from
-  file ...`.\n\nInstallation\n------------\n\n    /opt/chef/embedded/bin/gem install
-  chef-berksfile-env\n\nUsage\n-----\n\nIn your chef repo create a Berksfile next
-  to your Chef environment file like this,\n\n    chef-repo/environments/[ENV_NAME]/Berksfile\n\nThis
+  file ...`.\n\nView the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md)
+  to see what has changed.\n\nInstallation\n------------\n\n    /opt/chef/embedded/bin/gem
+  install chef-berksfile-env\n\nUsage\n-----\n\nIn your chef repo create a Berksfile
+  next to your Chef environment file like this,\n\n    chef-repo/environments/[ENV_NAME]/Berksfile\n\nThis
   is the default location that will used by the plugin. We have to put the Berksfile
   in its own\ndirectory since [multiple Berksfiles can't exist in the same directory](https://github.com/berkshelf/berkshelf/issues/1247).
   \n\nThe berksfile should include any cookbooks that your nodes or roles explicitly
@@ -132,7 +133,7 @@ description: "Chef-Berksfile-Env\n==================\n\nA Chef plugin which allo
   code on Chef's end effectively looks like this,\n\n    env.instance_eval(IO.read(env_ruby_file))\n\nwhich
   means that any context about the location of the environment file is lost. So we
   have no great way to discern the location of our environment \nRuby file, so instead
-  we guess."
+  we guess.\n"
 email:
 - bryan.baugher@cerner.com
 executables: []
@@ -164,7 +165,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.6
+rubygems_version: 2.6.14
 signing_key: 
 specification_version: 4
 summary: A Chef plugin to lock down your Chef Environment with a Berksfile