Skip to content
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

PutRecord Kinesis passing data does not handle the payload #86

Open
francoisneron opened this issue Apr 9, 2022 · 2 comments
Open

PutRecord Kinesis passing data does not handle the payload #86

francoisneron opened this issue Apr 9, 2022 · 2 comments

Comments

@francoisneron
Copy link

Kinesis node seems to not handle the data passed by other nodes or set values. It only supports static text in the form field.

@Palmeltveit
Copy link

Seems like this is pretty prevalent in this project. I had the same problems with the SQS node.

In the case of SQS, the value from the static form field is overridden if the input message has a "MessageBody"-value that is not null, which could be easily achieved using a function node. For Kinesis, it looks like adding a field with the name "Data" to the input message will give you the desired results. It would probably look something like:

return {
Data: JSON.stringify(msg.payload)
};

@Daniel-t
Copy link
Owner

All nodes are generated directly from the AWS API specification, so should behave the same way. One common issue I've seen (had myself in the start) is to make sure that the parameter names are exactly as specified in the AWS javascript api spec (case included). AWS api typically uses InitialUpperCase.

Unfortunately the api doesn't lend itself to chaining calls directly without a function or similar node

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants