add support for variable in message properties and message headers #80
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
|
I have revived this feature in the new RabbitMQ Integration Plugin: logstash-plugins/logstash-integration-rabbitmq#9 Since the Integration Plugin requires Logstash 6.5, I'd appreciate your input on backport requirements to get this feature working for you. |
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.
Hello,
This merge request fixes the same issue as #72 .
I just added the possibility to have variable in headers as well.
The example has been updated.
The tests has been updated as well to take this scenario into account.
However, I am totally new to Ruby, so someone should review it before merge.