-
Notifications
You must be signed in to change notification settings - Fork 167
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
Require rest-client 2.x, drop 1.x support code #269
Conversation
This reverts commit 15cd763.
+1 on the effort, haven't reviewed in detail. |
@@ -441,18 +441,6 @@ def api | |||
JSON.parse(response) | |||
end | |||
|
|||
def self.restclient_read_timeout_option |
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.
👍 🎉
kubeclient.gemspec
Outdated
@@ -27,7 +27,7 @@ Gem::Specification.new do |spec| | |||
spec.add_development_dependency 'webmock', '~> 3.0.1' | |||
spec.add_development_dependency 'vcr' | |||
spec.add_development_dependency 'rubocop', '= 0.49.1' | |||
spec.add_dependency 'rest-client' | |||
spec.add_dependency 'rest-client', '>= 2.0.0' |
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.
As discussed I'm fine with both ~> 2.0.0
or ~> 2.0
here.
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.
>= 2.0.0
was wrong as it would also accept 3.0.
Made it ~> 2.0
— will allow any 2.y.z; I don't want to pin to 2.0.z without specific reasons as rest-client is widely used gem...
Tests pass locally against:
- 2.0.0
- 2.0.2 (current)
- 2.1.0rc1
and rest-client is generally careful about backward compat so I think we can trust their semver.
I can make travis test against rest-client master in parallel to 2.0, if anyone wants.
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.
LGTM 👍
Backporting ManageIQ#223 bumped to rubocop with different defaults. These rubocop errors are fixed on master by ManageIQ#253 and ManageIQ#269 but we didn't backport those.
Backporting ManageIQ#223 bumped to rubocop with different defaults. These rubocop errors are fixed on master by ManageIQ#253 and ManageIQ#269 but we didn't backport those.
Closes #264.
Made it
~> 2.0
— will allow any 2.y.z; I don't want to pin to 2.0.z without specific reasons as rest-client is widely used gem (and my impression is they're careful about compatibility so we can trust their semver)...Tests pass locally against: