-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(integ-tests-alpha): awsApiCall failing for Kinesis putRecord - cannot properly pass Data #26798
Comments
Looks to be same as the issue this PR fixed #26797 |
Excellent, I will upgrade, verify, and close the issue if so. Thanks. |
Upgraded to 2.93.0, but the issue persists |
AWS SDK v3 has changed some data types to Uint8Array. If a value of this type was provided by the user, it would not be decoded properly back to a Uint8Array before making the call. Recognize when there is an encoded Uint8Array and decode it back properly. Closes #26798. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
AWS SDK v3 has changed some data types to Uint8Array. If a value of this type was provided by the user, it would not be decoded properly back to a Uint8Array before making the call. Recognize when there is an encoded Uint8Array and decode it back properly. Closes #26798. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Describe the bug
When I pass an expected
Uint8Array
to the params ofKinesis.putRecord
I receive the failure messageExpected Behavior
Put record should succeed with the input expected by the PutRecordCommandInput interface
Current Behavior
Here is the relevant log from the assertion lambda:
I think this is because the parameters are encoded with JSON.stringify which turns a Uint8Array into a JSON
Reproduction Steps
Create a test stack with a kinesis stream and put a record on it with
assertions.awsApiCall
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.93.0
Framework Version
No response
Node.js Version
18.12.0
OS
MacOS 13.5 (22G74)
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: