Actions
Bug #55460
closedGetBucketTagging returns wrong NoSuchTagSetError instead of NoSuchTagSet
% Done:
100%
Source:
Tags:
tagging backport_processed
Backport:
octopus pacific quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
it sounds like this was caused by an aws documentation bug, which previously mentioned NoSuchTagSetError even though the implementation returned NoSuchTagSet.
https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketTagging.html now says the NoSuchTagSet, and that matches https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html
see also:
https://github.com/ansible-collections/amazon.aws/pull/150
https://github.com/hashicorp/terraform-provider-aws/blob/e45aab12155799fd81bfb7ea66432dc0f5020e4a/internal/service/s3/tags.go#L35
Updated by Casey Bodley about 2 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 36856
Updated by Casey Bodley almost 2 years ago
- Pull request ID changed from 36856 to 46167
Updated by Daniel Gryniewicz almost 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot almost 2 years ago
- Copied to Backport #55612: octopus: GetBucketTagging returns wrong NoSuchTagSetError instead of NoSuchTagSet added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #55613: pacific: GetBucketTagging returns wrong NoSuchTagSetError instead of NoSuchTagSet added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #55614: quincy: GetBucketTagging returns wrong NoSuchTagSetError instead of NoSuchTagSet added
Updated by Backport Bot over 1 year ago
- Tags changed from tagging to tagging backport_processed
Updated by Konstantin Shalygin 5 months ago
- Status changed from Pending Backport to Resolved
- % Done changed from 0 to 100
Actions