Skip to content

Conversation

@AcidFlow
Copy link

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.

Paul Laturaze added 2 commits May 30, 2020 10:19
Define a configuration property `dynamoDBCustomEndpoint` to override
DynamoDB endpoint used by the Kinesis Client Library.
Define a configuration property `pathStyleAccessEnabled` to enable
path-style access to an S3 bucket.

The path-style access can be used for local development against mocked
services that do not support virtual-hosted access style.
## this can be used to specify local endpoints when using localstack
## this can be used to specify local endpoints when using localstack.
# customEndpoint = {{kinesisEndpoint}}
# dynamoDBCustomEndpoint = {{kinesisEndpoint}}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# dynamoDBCustomEndpoint = {{kinesisEndpoint}}
# dynamoDBCustomEndpoint = {{dynamoDBEndpoint}}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants