Aws-sdk-ruby: Suggestion to bump up dependency version of aws-sdk-core in aws-sdk-ssm gem

Created on 11 Jun 2020  路  14Comments  路  Source: aws/aws-sdk-ruby

Confirm by changing [ ] to [x] below to ensure that it's a bug:

Describe the bug

The new version of aws-sdk-ssm should have aws-sdk-core dependency increase to at least 3.99.0 on RubyGems because you added a new plugin (http_checksum) to CORE.

Gem name

aws-sdk-ssm 1.81.0
aws-sdk-core 3.97.0

To Reproduce (observed behavior)

  • install aws-sdk-core in the old version (<3.99.0)
  • install aws-sdk-ssm
  • after importing aws-sdk-ssm error occurs:
`require': cannot load such file -- aws-sdk-core/plugins/http_checksum.rb (LoadError)

Expected behavior

aws-sdk-ssm should have aws-sdk-core dependency >= 3.99.0

bug pwork-in-progress

Most helpful comment

All new gems have been published.

All 14 comments

I found aws-sdk-kms version 1.34.0 has the same issue. Must upgrade core manually.

        1: from /Users/anvo/.rvm/gems/ruby-2.5.3@tp_common/gems/aws-sdk-kms-1.34.0/lib/aws-sdk-kms/client.rb:27:in `require'
LoadError (cannot load such file -- aws-sdk-core/plugins/http_checksum.rb)

The same issue applies to the aws-sdk-cloudwatchlogs gem (I'm running 1.32.0), and I'm sure other gems as well.

Added PR #2329

Same issue with aws-sdk-secretsmanager gem.

We will yank gems. We have updated the minimum core version. We are very sorry about this.

Currently getting throttled by rubygems, unfortunately we have to yank 223 gems..

That is unfortunate. I suspect some people are blocked on deployments if they rely on things like aws-sdk-secretsmanager

Merged minimum core change + changelog entries for all gems - https://github.com/aws/aws-sdk-ruby/pull/2329

New release will start at 11 am. Yanking gems is a slow process. I tried automating it and got throttled.

There are ~30 remaining gems to yank (in progress). ETA for both removal of old gems and publishing of new gems is around 12pm PT.

looking forward

I just got the error Could not find aws-sdk-kms-1.34.0 in any of the sources when doing a ruby upgrade on an app. I got the message trying to run bundle. It was already pinned in my lockfile. I removed Gemfile.lock, ran gem install aws-skd-core (thanks @anvox) and the bundle succeeded. Just wanted to post here in case someone else runs into this issue.

All offending service gems have been yanked. They are currently being republished with a new minor version. A new aws-sdk-core version has also been published.

Very sorry about this. Our automation verifies against the latest set of gems. We will correct this to include edge cases with older core gems.

Fantastic! I see the update 1.34.1 is rolled out and it is working for me. You guys are great!
image

All new gems have been published.

Was this page helpful?
0 / 5 - 0 ratings