Describe the bug
There is a currently unreleased code change in the aws-partitions gem. I suspect this might be due to the gem's version not being revved in that commit (0ed223e9) or in the commits merged since.
Gem name:
aws-partitions v1.400.0 - v1.402.0
Version of Ruby, OS environment
Ruby 2.2 - 2.7
To Reproduce (observed behavior)
Steps to reproduce the behavior (please share code or minimal repo)
禄 gem list | grep aws-partitions
aws-partitions (1.402.0)
禄 irb
irb(main):001:0> require 'aws-sdk'
=> true
irb(main):002:0> Aws::Partitions.service_ids.keys.map do |service|
irb(main):003:1* Aws.const_get(service)
irb(main):004:1> end
Traceback (most recent call last):
7: from /Users/robbkidd/.asdf/installs/ruby/2.6.3/bin/irb:23:in `<main>'
6: from /Users/robbkidd/.asdf/installs/ruby/2.6.3/bin/irb:23:in `load'
5: from /Users/robbkidd/.asdf/installs/ruby/2.6.3/lib/ruby/gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>'
4: from (irb):2
3: from (irb):2:in `map'
2: from (irb):3:in `block in irb_binding'
1: from (irb):3:in `const_get'
NameError (uninitialized constant Aws::Profile)
Error appeared in the nightly the Honeycomb beeline-ruby integration tests starting on Dec 2 and continuing to today. The integration tests walk the collection of service_ids declared in Aws::Partitions and try to access the associated classes. Over the course of a few versions of the aws-partitions gem (1.400.0-1.402.0), Profile was removed from the gem to be added under a different name. 0ed223e9 appears to have one more removal left to release.
Thank you for reporting this. We thought we cleaned up everything around this. Long story short, an AWS service launched with "Profile" and it caused conflicts with CLI so SDK teams were forced to remove it and it was re-released as CustomerProfiles instead.
Github 'master' branch appears to be in good state. A new release is going out today with partitions changes, so I think that this should get resolved once that finishes.
Much love sent y'all's way. Totally understand how much fiddly work it is to undo code generation. Thanks for the quick response!
This appears to be fixed with 1.403.0. Re-open if it's still a problem for you.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Most helpful comment
This appears to be fixed with 1.403.0. Re-open if it's still a problem for you.