Skip to content
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

S3 ListObjectVersions ObjectVersionStorageClass type is incorrect #6609

Open
3 tasks done
rawpixel-vincent opened this issue Feb 27, 2024 · 5 comments
Open
3 tasks done
Assignees
Labels
bug This issue is a bug. p2 This is a standard priority issue s3 service-api This issue is due to a problem in a service API, not the SDK implementation.

Comments

@rawpixel-vincent
Copy link

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/[email protected]

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

@rawpixel-vincent rawpixel-vincent added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 27, 2024
@kuhe kuhe added the service-api This issue is due to a problem in a service API, not the SDK implementation. label Feb 27, 2024
@kuhe
Copy link
Contributor

kuhe commented Feb 27, 2024

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.

@kuhe kuhe removed the bug This issue is a bug. label Feb 27, 2024
@rawpixel-vincent
Copy link
Author

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

@aBurmeseDev aBurmeseDev removed the needs-triage This issue or PR still needs to be triaged. label Feb 27, 2024
@aBurmeseDev
Copy link
Member

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.

@aBurmeseDev aBurmeseDev added response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days. bug This issue is a bug. labels Feb 27, 2024
@rawpixel-vincent
Copy link
Author

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

@aBurmeseDev aBurmeseDev self-assigned this Feb 27, 2024
@aBurmeseDev aBurmeseDev transferred this issue from aws/aws-sdk-js-v3 Feb 27, 2024
@aBurmeseDev
Copy link
Member

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

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days. label Mar 1, 2024
@aBurmeseDev aBurmeseDev added the s3 label Mar 28, 2024
@zshzbh zshzbh transferred this issue from aws/aws-sdk Oct 30, 2024
@zshzbh zshzbh added the p2 This is a standard priority issue label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. p2 This is a standard priority issue s3 service-api This issue is due to a problem in a service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

4 participants