Integrating Custom Properties to ActiveMQEvent #375
Merged
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
smirnoal
approved these changes
Nov 11, 2022
lohithpc1
requested review from
smirnoal
and removed request for
msailes and
andclt
smirnoal
approved these changes
Nov 11, 2022
|
Thanks, LGTM |
andclt
approved these changes
Nov 11, 2022
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.
Issue #, if available:
Custom Properties Set by the customer are not being propagated to target function, as we don't have a properties field in here.
Description of changes:
Added properties field and also a unit test to see if we are getting right fields.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.