feat(s3): allow specifying storage class for PutObject #2440
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
@syhpoon Can you also run |
syhpoon
force-pushed
the
syhpoon/s3-storage-class
branch
from
75b89bf to
ee2511e
Compare
syhpoon
force-pushed
the
syhpoon/s3-storage-class
branch
from
ee2511e to
c78d4fe
Compare
@adityathebe done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow configuring S3 check to use a non-default storage class for PutObject.
The storage class is specified as a raw string to allow for new values in the future as well as non-AWS custom storage classes.