aws / aws-sdk

Landing page for the AWS SDKs on GitHub
https://aws.amazon.com/tools/
Other
68 stars 12 forks source link

S3 ListObjectVersions ObjectVersionStorageClass type is incorrect #705

Open rawpixel-vincent opened 4 months ago

rawpixel-vincent commented 4 months ago

Checkboxes for prior research

Describe the bug

the type of ObjectVersionStorageClass in the result output of ListObjectVersionsOutput.Versions[].StorageClass is allowing only "STANDARD", it should allow all possible storage class.

Screenshot 2024-02-27 at 13 06 36 Screenshot 2024-02-27 at 13 09 20 Screenshot 2024-02-27 at 13 09 11

SDK version number

@aws-sdk/client-s3@3.515.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

v20.11.0

Reproduction Steps

Request ListObjectVersionsCommand

example:

    const VS = await s3ClientApSoutheast1.send(
      new ListObjectVersionsCommand({
        Bucket: 'bucket-name',
      }),
    );

Observed Behavior

Versions[].StorageClass type is fixed to "STANDARD"

Expected Behavior

Versions[].StorageClass type should allow any valid storage class

Possible Solution

No response

Additional Information/Context

No response

kuhe commented 4 months ago

According to this service documentation, I only see STANDARD available: https://docs.aws.amazon.com/AmazonS3/latest/API/API_ObjectVersion.html.

If DEEP_ARCHIVE is indeed available, we have to wait for the service to push the model update to the SDKs.

rawpixel-vincent commented 4 months ago

Ahh I see that's a bug in the services documentation, what are the steps to move this there?

aBurmeseDev commented 4 months ago

Hi @rawpixel-vincent - you can directly reach out to service team via AWS Support or we can submit a request to service team on your behalf. Let us know if you'd like us to submit a request.

rawpixel-vincent commented 4 months ago

Hi, it's great if you don't mind forwarding this request on my behalf. Thank you

aBurmeseDev commented 4 months ago

Submitted a request to service team, and transferred the issue to our cross-SDK repo, please check back in for updates. (ref:P120170678)