Support setting an explicit prefix for the S3 store #7 fixed.#39
Open
omkarjoshi wants to merge 1 commit intoawslabs:masterfrom
Open
Support setting an explicit prefix for the S3 store #7 fixed.#39omkarjoshi wants to merge 1 commit intoawslabs:masterfrom
omkarjoshi wants to merge 1 commit intoawslabs:masterfrom
Conversation
Author
4n0nym1ty
approved these changes
Jul 6, 2023
|
Any progress on this? ;) |
4n0nym1ty
approved these changes
Sep 13, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Issue #7 :
Changes Covered:
Adding a separate method to allow custom s3key names to be specified if the same bucket needed to be used for multiple reasons. If custom key name is specified all the messages will be stored under that key/ bucket assuming access policies are present