Skip to content

apigatewayv2-http-kinesis-integration: do not expect EncryptionType for an unencrypted stream - #19

Merged
HarshCasper merged 1 commit into
masterfrom
fix/kinesis-put-record-smoke-test
Oct 19, 2026
Merged

HarshCasper merged 1 commit into
masterfrom
fix/kinesis-put-record-smoke-test

Conversation

@HarshCasper

Copy link
Copy Markdown
Member

The Makefile CI fails on apigatewayv2-http-kinesis-integration since early October. It is the only failing sample in the latest run now that the license problem is fixed:

API Response: {"ShardId":"shardId-000000000000","SequenceNumber":"4967940745588605767925297472063743257610882932624536371"}
Smoke test failed: The response does not contain the expected fields.

The smoke test required EncryptionType in the PutRecord response. Kinesis returns EncryptionType only for encrypted streams, and this sample's stream is not encrypted. LocalStack's parity test for this exact integration (HTTP API, Kinesis-PutRecord, recorded against AWS) shows AWS answering with ShardId and SequenceNumber only. The test passed while LocalStack returned "EncryptionType": "NONE"; LocalStack now answers like AWS. The smoke test now checks ShardId and SequenceNumber.

Tested locally with localstack/localstack-pro:latest (2026.10.0): make test-ci in the sample deploys the 9 resources and the smoke test passes.

…or an unencrypted stream

Kinesis PutRecord returns EncryptionType only for encrypted streams. The
smoke test required it, which only passed while LocalStack returned
"EncryptionType": "NONE"; LocalStack now answers like AWS (ShardId and
SequenceNumber), so the Makefile CI fails on this sample since early
October. Check ShardId and SequenceNumber only.

Claude-Session: https://claude.ai/code/session_01DZfDmzUBPqNAu3yFKyfCNM
@HarshCasper
HarshCasper merged commit 649bc92 into master Oct 19, 2026
1 check passed
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

Successfully merging this pull request may close these issues.

1 participant