New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump windows cookbook dependency #111
Conversation
Codecov Report
@@ Coverage Diff @@
## master #111 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 5
Lines 136 136
=====================================
Hits 136 136 Continue to review full report at Codecov.
|
metadata.rb
Outdated
@@ -9,7 +9,7 @@ | |||
issues_url 'https://github.com/cvent/octopus-deploy-cookbook/issues' | |||
version '0.12.0' | |||
|
|||
depends 'windows', '>= 1.38.0' | |||
depends 'windows', '>= 3.0.5' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually think we do not need the cookbook anymore. The main reason for having it was simply for backwards compatibility issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh forgot about the tools resource which does require it. I would prefer to just not specify a version here TBH and make it so its picked outside of this cookbook.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sever and tentacle don't, but it looks like tools still uses the windows_zipfile
resource which I believe does require the windows cookbook.
https://github.com/cvent/octopus-deploy-cookbook/blob/master/resources/tools.rb#L44-L48
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually I believe in pinning cookbook versions, however in this case I think you are right. The likelyhood users will run into dependency hell if they have other cookbooks that depend on the windows cookbook outweighs the risk that the windows_zipfile
resource api will break.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if the version >= 1.38.0 was needed or not, One thing you could do is add a dependency on windows >= 3.0.5 in the berksfile so that in testing it would use that version.
I've added windows cookbook dependency to berkshelf, and removed the version pin from the metadata file. |
836f3dd
to
0c278b6
Compare
Berksfile
Outdated
@@ -3,6 +3,8 @@ source 'https://supermarket.chef.io/' | |||
|
|||
metadata | |||
|
|||
cookbook 'windows', '~> 3.0.5' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we put this in the test group?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, pushed.
0c278b6
to
19f18dd
Compare
No longer required if using chef >=12.4
19f18dd
to
32abe47
Compare
Resolves issue #29
Bump windows cookbook version now that
windows_package
is part of chef 12.Windows cookbook 3.0.x no longer includes windows_package resource.
I intentionally didn't upgrade to 3.1.x since that version of the windows cookbook requires chef 12.7.x
The
windows_zipfile
has no breaking changes so there should be no change in behavior.https://github.com/chef-cookbooks/windows/blob/master/CHANGELOG.md