Improve Kinesis / S3 configuration to run against mock services #175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request aims at running the S3 loader locally against mocked services such as localstack or minio.
To be able to read from Kinesis, the KCL automatically creates a DynamoDB table to keep the stream offset. When running locally, the KCL DynamoDB endpoint should allow to be overridden through the configuration to point to a local DynamoDB.
This is done by introducing an optional
dynamoDBCustomEndpoint
in the Kinesis configuration. This property is then propagated to KCL configuration when it is defined.The second part of that pull request introduces a configuration property for the S3 client:
pathStyleAccessEnabled
. That flag allows to enable the path-style access on the S3 client, instead of the default virtual-hosted access style, which is not necessarily supported by mocked services such as localstack.