You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this scenario, the "message" variable is the entire queue message, and the "payload" variable is the decrypted content, which matches the declared message format {"attachments":{...},"data":{...},"metadata":{...}}. However, when checking whether to call the transform() function on the message, if it is a "before" transform, then the "message" object is passed, instead of the "payload" object. This causes the message to be unreadable when it reaches the actual action function.
Bug 2.
When inside of a transform, and the user wants to save the pre-transformed data to the raw-data-storage, the emitter currently sends:
As written above, the body key does not exist on the message object. This function needs to then be changed to send object.data instead of object.body in the payload.
The text was updated successfully, but these errors were encountered:
Bug 1.
Currently, in ferryman, when a message is received on the queue, the content buffer is decrypted and then passed to the callback function:
openintegrationhub/lib/ferryman/lib/ferryman.js
Lines 356 to 358 in dccbbce
In this scenario, the "message" variable is the entire queue message, and the "payload" variable is the decrypted content, which matches the declared message format
{"attachments":{...},"data":{...},"metadata":{...}}
. However, when checking whether to call the transform() function on the message, if it is a "before" transform, then the "message" object is passed, instead of the "payload" object. This causes the message to be unreadable when it reaches the actual action function.Bug 2.
When inside of a transform, and the user wants to save the pre-transformed data to the raw-data-storage, the emitter currently sends:
openintegrationhub/lib/ferryman/lib/transformer.js
Lines 21 to 24 in dccbbce
As written above, the body key does not exist on the message object. This function needs to then be changed to send object.data instead of object.body in the payload.
The text was updated successfully, but these errors were encountered: