Make the key generator configurable #21
Open
Conversation
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
|
Also looking for this feature |
|
+1 |
1 similar comment
|
+1 |
|
Are there any plans on merging this PR or any of the others addressing this feature gap? If a different design is desired, can the maintainers provide feedback? In many setups it's very desirable being able to use an existing bucket where similar data is stored and managed, as well as to avoid reaching the max number of buckets an account can have. |
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
Needed if you want a key that is prepended with a path within the bucket.
Right now we have to capture the message in a delegating SQS client, re-write the JSON, and do something equally ugly for S3.
Cheers!