Add new parameter skip_munging for rabbitmq_parameter #3
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.
Pull Request (PR) description
Add new parameter
skip_munging
forrabbitmq_parameter
to prevent numberic strings from being converted to integers.This Pull Request (PR) fixes the following issues
We have several
x-content-hash
exchanges which use a numeric string as the routing key. As a result, shovels for these exchanges would include key value pairs like this"src-exchange-key": "5"
. By default the string"5"
will be converted to an integer. However, RabbitMQ doesn't accept exchange keys to be integers. As a result, we'd run into errors from RabbitMQThis PR would allow the auto type conversion to be disabled and therefore numeric strings to be included in the RabbitMQ parameter payload if needed.