AWS S3: Do not require Write permissions #753
Merged
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
…PI. Fail on demand only.
ggallotti
temporarily deployed
to
external-storage-tests
GitHub Actions
Inactive
ggallotti
changed the title
Cherry pick to beta success |
claudiamurialdo
approved these changes
Jan 17, 2023
claudiamurialdo
approved these changes
Jul 3, 2023
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.
AWS S3 Client Storage should not need full permissions to the Bucket. (GETObject* IAM policy should work)
Problem
We must not create the Folder on init, not even in any Upload/Copy operation. Folders are not required to be created in advance.