This repository has been archived by the owner on Nov 14, 2020. It is now read-only.
Fix argument order in function call for policy updates #18
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
jtopjian
approved these changes
Jun 27, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I ran into bug where attempting to apply policy updates would result in 404 errors being returned from the RabbitMQ API. In the call to
putPolicy()fromUpdatePolicy(), t he argument order was wrong, passing in thevhostvalue into theuserargument and vice-versa (comparatively, the correct call is made inCreatePolicy()). Fixing the order resolved the issue with 404 being issued by the RabbitMQ API.