-
Notifications
You must be signed in to change notification settings - Fork 897
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
Update dependencies to match new fog-google #17258
Conversation
@miq-bot add_label wip |
e50779c
to
d08636c
Compare
Checked commit tumido@d08636c with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@miq-bot remove_label wip |
cc @bdunne @NickLaMuro is it okay to just change the version in the gemspec for our mime-types-redirector? |
@agrare eww.... I would have to look. There might be some APIs used in this new version that might not match. I can look in a bit. Thanks for the heads up. |
@NickLaMuro yeah that's what I was worried about 😟 |
@agrare Okay, so quick And it only uses I need to check if the |
@agrare @tumido Okay, I checked the changes between I ✌️ think ✌️ that you will be okay. |
Also, |
Thanks for digging into this @NickLaMuro ! |
@NickLaMuro yes, I confirm, this change is required just because it's |
@tumido Just to clarify, I wasn't under the impression that Take for example the Plus, I am pessimistic about other developers and their code... call me a curmudgeon... ¯\_(ツ)_/¯ |
@NickLaMuro, I know, my dear curmudgeon! 😃 It's always better to be super cautious and get to the root of things... I honestly don't understand the background here (why the gem is overridden this way etc.) so I'm totally ok with any suggestion and raised concerns. Actually I'm not happy at all I had to do this PR since I don't see that far about what all the outcomes can be - especially since it's a permanent change and some other gem can resolve to this 3.0 version and try to leverage it's functionality, which might be missing... And all this just because one call in I totally can see, how you got that curmudgeon name, haha. |
Oh, glad you asked So this PR against the rest-client/rest-client#557 (rebased by Jason here) Effectively, just to load/ The point of this wrapper is effectively to leverage the lighter weight "mime gem" in our application, which is historically a large ruby process just by default. The wrapper effectively takes the (frantically goes and updates the PR description with links and context...) Unfortunately, there are many downsides to this approach, and your confusion (along with pretty much everyone else's) is chiefly among them. But, you know, that whole "hindsight" thing and whatnot... |
@agrare @NickLaMuro I assume this can be |
@simaishi I don't have a problem with it but we should make sure gaprindashvili will bundle with this version bumped before backporting. |
yup, we're bringing ManageIQ/manageiq-providers-google#54 into Gaprindashvili. |
Update dependencies to match new fog-google (cherry picked from commit 437ea65) https://bugzilla.redhat.com/show_bug.cgi?id=1585821
Gaprindashvili backport details:
|
@miq-bot add_label fine/yes @simaishi Adding this to fine since it's a dependency for the ManageIQ/manageiq-providers-google#54 |
Update dependencies to match new fog-google (cherry picked from commit 437ea65)
Fine backport details:
|
Update dependencies to match new fog-google (cherry picked from commit 437ea65)
In order to upgrade
fog-google
in google provider, it is required to upgrade themime_types
in our core as well.Dependency chain:
"fog-google", "~> 1.3.3"
"google-api-client", "~> 0.19.1"
"mime-types", "~> 3.0"
Related: ManageIQ/manageiq-providers-google#54