Adding HTTP Client and TTLPolicyManager with fallback to queue-ttl #12
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
…fault false Signed-off-by: Fawzi Essam <iifawzie@gmail.com>
Signed-off-by: Fawzi Essam <iifawzie@gmail.com>
github-actions bot
pushed a commit
that referenced
this pull request
Nov 9, 2025
# [1.1.0](v1.0.3...v1.1.0) (2025-11-09) ### Features * Adding HTTP Client and TTLPolicyManager with fallback to queue-ttl ([#12](#12)) ([2759a2c](2759a2c))
|
🎉 This PR is included in version 1.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Description
This PR introduces support for using RabbitMQ policies to manage TTL for delay queues, instead of relying on queue-level TTL settings. Fixes #10
Key changes:
Maintains full compatibility with existing versions, with default, false.
Motivation:
Hard-coding TTL in queues requires manual queue deletion/re-declaration to change delays, which is error-prone and inconvenient. Using policies allows TTLs to be updated on-the-fly, providing a more robust and maintainable solution.