feat: Add support for starting position AT_TIMESTAMP to MSK events #12034
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.
Closes: #12033
Add support for a StartingPosition of AT_TIMESTAMP to MSK event source mappings. When this configuration is used,
StartingPositionTimestamp must also be provided, in Unix Time seconds, which is consistent with the existing support in the
kafka
eventSupport for this starting position has recently been added to AWS Lambda event source mappings using MSK
(https://aws.amazon.com/about-aws/whats-new/2023/06/aws-lambda-starting-timestamp-kafka-sources/)
Since
runServerless
tests are expensive, test the happy path in the existing test of a valid configuration rather than adding an explicit separate test for it, but add a new test to explicitly verify the unhappy path in which a timestamp at which to start is not provided