Closed lyoung-confluent closed 10 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
58da2cc
) 73.30% compared to head (51690ab
) 73.30%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
I'm unsure if this should be a new struct specifically for 2.0 or just a small modification to the existing struct as implemented in this PR.
Since the new schema version removes a field, rather than being purely additive, let's do new structs with a V2
suffix.
@bmoffatt I've split it into a new struct S3BatchJobV2
, however the response struct has not changed with 2.0, should I duplicate it anyway?
@bmoffatt I've split it into a new struct
S3BatchJobV2
, however the response struct has not changed with 2.0, should I duplicate it anyway?
I'd say leave the response struct as-is
This PR adds support for the new S3 Batch Job 2.0 Invocation Schema by adding the
userArguments
field and thes3Bucket
key (instead ofs3BucketArn
) to the existingS3BatchJob
andS3BatchJobTask
structs. For more details see this blog post: https://aws.amazon.com/blogs/storage/automate-object-processing-in-amazon-s3-directory-buckets-with-s3-batch-operations-and-aws-lambda/~I'm unsure if this should be a new struct specifically for 2.0 or just a small modification to the existing struct as implemented in this PR. Lambda Powertools for Python has implemented it as the same object/class for both schema versions but also has the benefit of Python's looser typing: https://github.com/aws-powertools/powertools-lambda-python/pull/3572~
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.