chore(lambda-event-sources): starting position timestamp for kafka #31439
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.
Reason for this change
It was impossible to start consuming a Kafka topic from a specific point in time.
Description of changes
The user may now set
startingPositionTimestamp
toManagedKafkaEventSource
andSelfManagedKafkaEventSource
to start consuming a Kafka topic from a specific point in time.Lambda and CloudFormation have supported the functionality for a while, and other stream event sources like
KinesisEventSource
already had a CDK implementation for it, so there's nothing new under the sky — just expanding it to cover sources we are using :)Description of how you validated changes
The change is tested by adding similar unit tests to other event sources supporting this functionality.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license