Support FIFO queues in shoryuken sqs commands
#473
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
The `message_deduplication_id` and `message_group_id` are now preserved when dumping, moving and requeuing messages. Note: if a message is re-queued during the 5-minute deduplication window, SQS will detect it as a duplicate, accept and suppress it. To avoid this, run `sqs dump` and edit the resulting `.jsonl` file to change the `message_deduplication_id` for all affected messages.
|
@ocisly thanks! Added to master 🍻 |
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.
The
message_deduplication_idandmessage_group_idare now preservedwhen dumping, moving and requeuing messages.
Note: if a message is re-queued during the 5-minute deduplication
window, SQS will detect it as a duplicate, accept and suppress it.
To avoid this, run
sqs dumpand edit the resulting.jsonlfile tochange the
message_deduplication_idfor all affected messages.Fixes #470