S3: adds custom deserializer for get-bucket-location operation

[skotambkar]

• Code generates a custom deserializer for s3: get-bucket-location api operation. This implementation differs from how v1 sdk handles custom deserialization. V1 uses regex matching on response. In this change, we make use of already generated deserializer functions.

• Adds unit test to validate the change.

• Fixes LocationRestraint always empty on GetBucketLocation call #908

[Chandrian]

probably related, but just in case, putting it here. To work around this issue, I was trying to use HeadBucket and get the value of the "X-Amz-Bucket-Region" header, but getting the following error message:

failed to call service: S3, operation: HeadBucket, error: https response error StatusCode: 301, RequestID: xxx, HostID: xxx, api error MovedPermanently: Moved Permanently

[jasdel]

Hi @Chandrian I suggest using the SDK's feature/s3/manager#GetBucketRegion utility instead of the API call directly. The HeadBucket and GetBucketLocation operations have some unexpected behavior depending on how they are called. The SDK's GetBucketRegion utility takes care of that and should always be able to return the region a bucket was created in.

[Chandrian]

Hi @Chandrian I suggest using the SDK's feature/s3/manager#GetBucketRegion utility instead of the API call directly. The HeadBucket and GetBucketLocation operations have some unexpected behavior depending on how they are called. The SDK's GetBucketRegion utility takes care of that and should always be able to return the region a bucket was created in.

Thank you, GetBucketRegion is working perfectly