-
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::S3::Client#get_bucket_lifecycle_configuration raise NotImplementedError #1764
Comments
Can you share your |
Just s soft update, I can reproduce this, looks like an issue when our xml parser is expecting 'Tag' while provided with a 'Key', still investigating |
Thank you for your response.
Please confirm following. GEM
remote: https://rubygems.org/
specs:
aws-partitions (1.80.0)
aws-sdk-core (3.19.0)
aws-partitions (~> 1.0)
aws-sigv4 (~> 1.0)
jmespath (~> 1.0)
aws-sdk-kms (1.5.0)
aws-sdk-core (~> 3)
aws-sigv4 (~> 1.0)
aws-sdk-s3 (1.9.1)
aws-sdk-core (~> 3)
aws-sdk-kms (~> 1)
aws-sigv4 (~> 1.0)
aws-sigv4 (1.0.2)
coderay (1.1.2)
jmespath (1.4.0)
method_source (0.9.0)
pry (0.11.3)
coderay (~> 1.1.0)
method_source (~> 0.9.0)
PLATFORMS
ruby
DEPENDENCIES
aws-sdk-s3 (~> 1)
pry
BUNDLED WITH
1.16.1 Regards, |
PR #1766 addressing the fix is opened for review |
PR has been merged, will be out in the next release |
aws-sdk-core Release 3.20.1 containing the fix is out, closing, feel free to reopen with further questions or issues |
Issue description
When I test the following code, Aws::S3::Client#get_bucket_lifecycle_configuration, it raises NotImplementedError instead of getting lifecycle_configurations.
I confirmed that this phenomenon occurs only when filter.and.tags is set in lifecycle configuration of Bucket. Please see "Code snippets / steps to reproduce".
Gem name ('aws-sdk', 'aws-sdk-resources' or service gems like 'aws-sdk-s3') and its version
Version of Ruby, OS environment
Code snippets / steps to reproduce
Bucket lifecycle configuration
Run Test
$ bundle exec ruby s3_test.rb ng-bucket
backtrace will be like following.
Please confirm.
The text was updated successfully, but these errors were encountered: