-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support processing response data in custom trigger multi-pipeline #958
Comments
@gao270615179 , please provide more detail for what you are asking for here. An example of your use case always helps. |
@gao270615179 this needed some refactoring as the multi-pipeline stuff represented a big shift for the custom triggers. This was addressed as part of #967 (WIP) via a new MessageReceived method. The method takes an additional per-pipeline response handler. Would love to know if this would work for what you have in mind. |
Share functionality between custom and built-in triggers, expanding testability of those built-in. Also adds support for handling per-pipeline response data. fixes edgexfoundry#960 fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
Share functionality between custom and built-in triggers, expanding testability of those built-in. Also adds support for handling per-pipeline response data to custom triggers. fixes edgexfoundry#960 fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
@AlexCuse This is what I need. I will test this commit. Thanks! |
Moved issue to Ice Box for now as the PR is on hold and will be addressed in the Kamakura dev cycle |
Enable passing a handler to process pipeline responses when invoking runtime from a custom trigger. fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
Enable passing a handler to process pipeline responses when invoking runtime from a custom trigger. fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
@gao270615179 did you ever test using the branch above - we are going to try to get the custom |
Enable passing a handler to process pipeline responses when invoking runtime from a custom trigger. fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
Enable passing a handler to process pipeline responses when invoking runtime from a custom trigger. fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
Enable passing a handler to process pipeline responses when invoking runtime from a custom trigger. fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
@AlexCuse Sorry, I'm late for testing. I have test the commit AlexCuse@e0d616d. It's useful for me. |
Enable passing a handler to process pipeline responses when invoking runtime from a custom trigger. fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
…#989) Enable passing a handler to process pipeline responses when invoking runtime from a custom trigger. fixes #958 Signed-off-by: Alex Ullrich <[email protected]> Co-authored-by: Lenny Goodell <[email protected]>
Share functionality between custom and built-in triggers, expanding testability of those built-in. Also adds support for handling per-pipeline response data to custom triggers. fixes edgexfoundry#960 fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]>
…edgexfoundry#989) Enable passing a handler to process pipeline responses when invoking runtime from a custom trigger. fixes edgexfoundry#958 Signed-off-by: Alex Ullrich <[email protected]> Co-authored-by: Lenny Goodell <[email protected]>
Support processing response data in custom trigger multi-pipeline
The text was updated successfully, but these errors were encountered: