exact queue name option #393
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
michaelklishin
requested changes
May 6, 2024
Member
michaelklishin
left a comment
michaelklishin
left a comment
There was a problem hiding this comment.
This is a reasonable addition but the name "exact" does not explain what the option really does.
"Do not add namespace" may be longer but is more specific (and I am fine with longer names).
Contributor
Author
|
how about |
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.
Sometimes we want to bind to an exact queue name without using the namespace.
For example, for most of our consumers we want to use the application name as a prefix to help group queues. However, we have a global 'deadletter' queue which we do not want to namespace, but connect to verbatim.
This PR allows
exact: trueto be added when setting the queue_name in a consumer.