-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
aws-sdk-s3 version 1.165.0 invalid configuration option #3113
Comments
Thanks for reporting this and for the great reproduction. It looks like the issue is caused by the recent autoload PR (#3105) which adds autoload for service clients. Service client's on require add their service identifier to the global config plugin's list of identifiers which it uses to filter out config (example from s3: I'll get a fix out today, but in the mean time, you can get around this by using S3 Client (eg just a Aws.config[:s3] = {
stub_responses: {
get_object: true,
put_object: true
}
}
Aws::S3.const_get(:Client) # this triggers the autoload and ensures s3's service id is added to the global config plugin.
Aws::CloudFormation::Client.new(
region: "us-east-1",
credentials: Aws::Credentials.new("foo", "bar")
) |
Perfect, thanks @alextwoods! |
(Confirmed, that does indeed fix my problem.) |
We've released the fix - [email protected] and later should no longer have this issue. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
Stubbing s3 and then initializing a cloudformation client fails.
Regression Issue
Expected Behavior
I expect this to succeed the same as previous versions.
Current Behavior
It gives an argument error.
Reproduction Steps
Here is a test that fails on the latest s3 client:
If you switch the comments to use 1.164.0, it will work.
Possible Solution
No response
Additional Information/Context
No response
Gem name ('aws-sdk', 'aws-sdk-resources' or service gems like 'aws-sdk-s3') and its version
aws-sdk-s3 and aws-sdk-cloudformation
Environment details (Version of Ruby, OS environment)
3.4.0-dev, macOS
The text was updated successfully, but these errors were encountered: