You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2018. It is now read-only.
The SDK raises an error extending from Aws::Errrors::ServiceError for all 400 and 500 level responses. In this particular scenario, the service returns a 404 response. This is the same response status code returned when you attempt to access a non-existent bucket. Rather than try to special case these by parsing the error message, the SDK only returns the structured response data for "successful", 200 level responses.
We are currently exploring how to add a higher level abstraction over these client methods. It would be feasible to address this there.
I'm going to close this issue for now as we will not be making changes to this particular operation. I have started work on the higher level abstractions for the services. I'll be blogging (http://ruby.awsblog.com/) about these soon, and I'll publish my work-in-progress ideas to a branch as well.
I expected when making this call without a tag on a bucket-
@s3.get_bucket_tagging(:bucket => 'my_bucket')
That it would return a nil tagset, not that it would throw this error-
Aws::S3::Errors::NoSuchTagSet: The TagSet does not exist
Happy to rescue errors but I would much rather have it return a nil tagset in this case.
The text was updated successfully, but these errors were encountered: