Support for routing a response to another pipeNot planned
When posting data to a service, it will sometimes return an array with e.g. an id, and a status on the individual record. This result can be merged back (correlated) into the source pipe in Sesam. That way it is possible to take further action on each record based on the result from the post operation.
This is used when the target api doesn't have GET operations that can support the correlation behavior.
We currently implement this as a feature in microservices, where we push the result to a http pipe (using the sesam api and a token). This works, but it creates a weak link (not visual/tracked) between the system that receives the response and the pipe it is pushed to.
This is useful feedback. There has been several parties asking for similar features. We have not yet decided or figured out how to support it. It is not unlikely that the REST sink will get a feature like that at some point, but there are no concrete plans for supporting this yet.Comment actions
Please sign in to leave a comment.