fix: connect to the configured RabbitMQ vhost - #63
Open
SamuelGoulart wants to merge 1 commit into
Open
SamuelGoulart wants to merge 1 commit into
SamuelGoulart wants to merge 1 commit into
Conversation
setCredentials wasn't receiving virtualHost, so connections landed on the default RabbitMQ vhost instead of the configured one. Any exchange that happens to share a name on both vhosts will accept publishes without error while the message never reaches the intended queue. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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 fix passes
virtualHosttosetCredentialsso the RabbitMQ connection is opened on the vhost configured viaRABBIT_VIRTUAL_HOST, instead of always falling back to the default vhost (/).What type of PR contains?
This pull request closes the following issues:
Fixes #62