Skip to content
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 aws-sdk gem to v3 #488

Merged
merged 9 commits into from
Oct 21, 2019
Merged

Conversation

AlexanderZagaynov
Copy link
Contributor

@AlexanderZagaynov AlexanderZagaynov commented Sep 21, 2018

@@ -13,7 +13,7 @@ Gem::Specification.new do |s|

s.files = Dir["{app,config,lib}/**/*"]

s.add_dependency("aws-sdk", ["~>2.9.7"])
s.add_dependency("aws-sdk", ["~> 3"])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment regarding the gem version, and also remove all of the parens and square brackets (go for consistency with the lines below)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@AlexanderZagaynov AlexanderZagaynov force-pushed the aws_sdk_v3 branch 2 times, most recently from 404c1be to ab899ac Compare September 21, 2018 11:44
Copy link
Member

@NickLaMuro NickLaMuro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AlexanderZagaynov When the other gem dependency PRs are merged and travis can start running again, I am guessing that #434 is going to start failing, and that PR and #432 are going to have to be removed.

Thinking you probably can wait on that until I am correct in that assumption, but know that it will probably be something you need end up doing in the end.

@AlexanderZagaynov
Copy link
Contributor Author

@NickLaMuro If you mean I should revert / adopt those commits - I'll do.
There is several testing issues anyway, need to change more.

@AlexanderZagaynov
Copy link
Contributor Author

AlexanderZagaynov commented Sep 26, 2018

@NickLaMuro that was fixed in aws/aws-sdk-ruby#1760, thanks to @Fryguy :)

https://github.com/aws/aws-sdk-ruby/blob/22f10bed9c6cfb3317b9fc684c124168c5dca71e/gems/aws-sdk-core/lib/seahorse/client/net_http/connection_pool.rb#L262

So, I'm simply remove that patch entirely.

@AlexanderZagaynov
Copy link
Contributor Author

@miq-bot add_label gaprindashvili/yes
@miq-bot add_label hammer/yes

@Fryguy
Copy link
Member

Fryguy commented Oct 11, 2018

Aside from my comment above, this LGTM. @NickLaMuro not sure why you have a request change on this, but what do you think now?

@NickLaMuro
Copy link
Member

@Fryguy was mostly using that as a reminder that the PRs that I merged to patch aws-sdk have been reverted:

11f987f
1879e5c

Which they have.

But also, that I was suggesting that we wait to confirm the tests failed when the other PRs have been fixed, addressed and merged, since those should be merge-able without requiring other PRs to work. Reason being is that test is in there to confirm we don't have a regression since the fix ( #432 ) really didn't provide a spec of it's own to validate.

Since it seems that amazon_ssa_support also has a manageiq-gems-pending dependency, and merging these separately would basically cause developers to not be able to bundle for a period of time, waiting to do the above might not be possible.


Anyway, I will remove my ❌ since it doesn't seem like there is an easy solution for this.

@AlexanderZagaynov
Copy link
Contributor Author

AlexanderZagaynov commented Oct 12, 2018

@NickLaMuro other repos were updated as well.
Check the base issue, it has all the links: #465 and test logs.

@NickLaMuro
Copy link
Member

@AlexanderZagaynov I am referring to why Travis is currently failing:

Fetching gem metadata from https://rubygems.org/.
Resolving dependencies.......
Bundler could not find compatible versions for gem "aws-sdk":
  In Gemfile:
    manageiq-gems-pending (> 0) was resolved to 0.1.0, which depends on
      aws-sdk (~> 2.9.7)
    manageiq-providers-amazon was resolved to 0.1.0, which depends on
      aws-sdk (~> 3.0)

To get this to pass prior to merging this (in CI), and do what I suggested in the previous comment would probably have some undesirable affects for the rest of the team in the mean time.

Again, I removed my "Request changes" review.

@djberg96
Copy link
Contributor

@AlexanderZagaynov What's the word?

@AlexanderZagaynov
Copy link
Contributor Author

AlexanderZagaynov commented Jan 28, 2019

@djberg96
in a month :)

Alexander Zagaynov added 3 commits October 11, 2019 13:56
…monkey-patch-spec"

This reverts commit a08595f, reversing
changes made to ce647bc.
…aws-sdk-core-for-proxy-auth-fix"

This reverts commit 2b2c87f, reversing
changes made to beed01f.
@djberg96
Copy link
Contributor

@AlexanderZagaynov I think you'll need to update the gemspec, too.

@AlexanderZagaynov
Copy link
Contributor Author

@djberg96
Copy link
Contributor

@AlexanderZagaynov Oh, I didn't see it. I guess it's gems-pending that's the culprit.

@miq-bot
Copy link
Member

miq-bot commented Oct 17, 2019

Checked commits AlexanderZagaynov/manageiq-providers-amazon@32d337d~...8be7e04 with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0
6 files checked, 0 offenses detected
Everything looks fine. 🍰

@AlexanderZagaynov
Copy link
Contributor Author

All tests are green on my machine with patched versions of all gems mentioned here.

@AlexanderZagaynov
Copy link
Contributor Author

@Fryguy @NickLaMuro @agrare please review

@agrare
Copy link
Member

agrare commented Oct 21, 2019

Will merge when the cross-repo test is green https://travis-ci.org/agrare/manageiq-cross_repo/builds/600907361

@agrare agrare self-assigned this Oct 21, 2019
@agrare agrare merged commit 9e84410 into ManageIQ:master Oct 21, 2019
@agrare agrare added this to the Sprint 123 Ending Oct 28, 2019 milestone Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade AWS SDK library to version 3
6 participants