chef-berksfile-env 1.4.0 → 1.5.0

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 (4) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +3 -1
  3. data/VERSION +1 -1
  4. metadata +14 -13
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 3f4c0db5a76ae24775f0f45365c8777516b6598f
4
- data.tar.gz: 06ac854893dda9d92a30e053fd17d0a3401a208a
3
+ metadata.gz: 1b9336d11321950aab1d03e24cf3c1d9eb218975
4
+ data.tar.gz: bb0409c3f4d7276d7424f36b90e18377bf3d75bc
5
5
  SHA512:
6
- metadata.gz: 1f9a68e6c609813b1e90e3820dc1ecbf0f153eb6ba545853878a2f52922d30cadd5e9ec18f53f208332aa8df9d103d2ac7672f08953b7f99f4379a2c82cb0e50
7
- data.tar.gz: 7adf14f6fb70976d17e2f299b396bc2c82fb011d0f810304c66a443ec29f39e254d74eabf4e5530f1b5e5b5a6a6a8a6597d8e8badc972beb4d68c7bf9e3f012b
6
+ metadata.gz: 84926598e14f3f6ec722f48c1bfd22b531dbdddd89254a7ac09ae9639d84784adf3a6227c2fce10f76529208c49a4645f898fd4338e13bc7ba58618992ce6f6f
7
+ data.tar.gz: c6e81c0d2b2a0b8ad790be98cc08af75f4d6461fae333ebbbf5022682f0d667bd42bcc302bd06d51877c593ab4839099c86344630fe9481b7384b8f4691f035c
data/README.md CHANGED
@@ -5,6 +5,8 @@ A Chef plugin which allows you to lock down your Chef Environment's cookbook ver
5
5
 
6
6
  This is effectively the same as doing `berks apply ...` but via `knife environment from file ...`.
7
7
 
8
+ View the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md) to see what has changed.
9
+
8
10
  Installation
9
11
  ------------
10
12
 
@@ -76,4 +78,4 @@ So why do we do this? Well the only way to use this plugin is if your environmen
76
78
  env.instance_eval(IO.read(env_ruby_file))
77
79
 
78
80
  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
79
- Ruby file, so instead we guess.
81
+ Ruby file, so instead we guess.
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.4.0
1
+ 1.5.0
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: chef-berksfile-env
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.4.0
4
+ version: 1.5.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Bryan Baugher
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-09-27 00:00:00.000000000 Z
11
+ date: 2018-05-04 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: berkshelf
@@ -19,7 +19,7 @@ dependencies:
19
19
  version: '4.0'
20
20
  - - "<"
21
21
  - !ruby/object:Gem::Version
22
- version: '6.0'
22
+ version: '8.0'
23
23
  type: :runtime
24
24
  prerelease: false
25
25
  version_requirements: !ruby/object:Gem::Requirement
@@ -29,27 +29,27 @@ dependencies:
29
29
  version: '4.0'
30
30
  - - "<"
31
31
  - !ruby/object:Gem::Version
32
- version: '6.0'
32
+ version: '8.0'
33
33
  - !ruby/object:Gem::Dependency
34
34
  name: chef
35
35
  requirement: !ruby/object:Gem::Requirement
36
36
  requirements:
37
37
  - - ">="
38
38
  - !ruby/object:Gem::Version
39
- version: '11.0'
39
+ version: '12.0'
40
40
  - - "<"
41
41
  - !ruby/object:Gem::Version
42
- version: '13.0'
42
+ version: '15.0'
43
43
  type: :runtime
44
44
  prerelease: false
45
45
  version_requirements: !ruby/object:Gem::Requirement
46
46
  requirements:
47
47
  - - ">="
48
48
  - !ruby/object:Gem::Version
49
- version: '11.0'
49
+ version: '12.0'
50
50
  - - "<"
51
51
  - !ruby/object:Gem::Version
52
- version: '13.0'
52
+ version: '15.0'
53
53
  - !ruby/object:Gem::Dependency
54
54
  name: bundler
55
55
  requirement: !ruby/object:Gem::Requirement
@@ -95,9 +95,10 @@ dependencies:
95
95
  description: "Chef-Berksfile-Env\n==================\n\nA Chef plugin which allows
96
96
  you to lock down your Chef Environment's cookbook versions with a Berksfile.\n\nThis
97
97
  is effectively the same as doing `berks apply ...` but via `knife environment from
98
- file ...`.\n\nInstallation\n------------\n\n /opt/chef/embedded/bin/gem install
99
- chef-berksfile-env\n\nUsage\n-----\n\nIn your chef repo create a Berksfile next
100
- to your Chef environment file like this,\n\n chef-repo/environments/[ENV_NAME]/Berksfile\n\nThis
98
+ file ...`.\n\nView the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md)
99
+ to see what has changed.\n\nInstallation\n------------\n\n /opt/chef/embedded/bin/gem
100
+ install chef-berksfile-env\n\nUsage\n-----\n\nIn your chef repo create a Berksfile
101
+ next to your Chef environment file like this,\n\n chef-repo/environments/[ENV_NAME]/Berksfile\n\nThis
101
102
  is the default location that will used by the plugin. We have to put the Berksfile
102
103
  in its own\ndirectory since [multiple Berksfiles can't exist in the same directory](https://github.com/berkshelf/berkshelf/issues/1247).
103
104
  \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
132
133
  code on Chef's end effectively looks like this,\n\n env.instance_eval(IO.read(env_ruby_file))\n\nwhich
133
134
  means that any context about the location of the environment file is lost. So we
134
135
  have no great way to discern the location of our environment \nRuby file, so instead
135
- we guess."
136
+ we guess.\n"
136
137
  email:
137
138
  - bryan.baugher@cerner.com
138
139
  executables: []
@@ -164,7 +165,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
164
165
  version: '0'
165
166
  requirements: []
166
167
  rubyforge_project:
167
- rubygems_version: 2.6.6
168
+ rubygems_version: 2.6.14
168
169
  signing_key:
169
170
  specification_version: 4
170
171
  summary: A Chef plugin to lock down your Chef Environment with a Berksfile