feat(blob): add support for access and improve s3 driver #709
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.
This pull request introduces support for specifying access levels ('public' or 'private') when uploading blobs, with initial implementation for S3 and partial handling for other drivers. It updates the documentation, types, and driver logic to accommodate this feature, while ensuring backward compatibility and providing clear warnings or errors for unsupported configurations.
Access Level Support for Blob Uploads
accessfield toBlobPutOptionsandBlobMultipartOptionstypes, allowing users to specify'public'or'private'access when uploading blobs. [1] [2]docs/content/docs/2.features/0.blob.md) to describe the newaccessoption, noting that only the S3 driver currently supports it.S3 Driver Enhancements
accessoption in the S3 driver: setting'public'adds the appropriate ACL header (x-amz-acl: public-read) to make the blob public.Other Driver Handling
accessoption is used, indicating that access level is not supported and will be ignored.'private'access is requested, as this is not yet supported.