fix(lambda): bump @aws-lambda-powertools/logger from 1.10.0 to 1.12.1 in /lambdas

[dependabot]

Bumps @aws-lambda-powertools/logger from 1.10.0 to 1.12.1.

Release notes

Sourced from @​aws-lambda-powertools/logger's releases.

v1.12.1

Summary

This release brings another new utility to Powertools for AWS Lambda (TypeScript): introducing the Batch Processing utility ✨ The release also improves the Logger utility, which can now include the cause field in error logs.

Batch Processing Beta

Warning This utility is currently released as beta developer preview and is intended strictly for feedback and testing purposes and not for production workloads. The version and all future versions tagged with the -beta suffix should be treated as not stable. Up until before the General Availability release we might introduce significant breaking changes and improvements in response to customers feedback.

The batch processing utility handles partial failures when processing batches from Amazon SQS, Amazon Kinesis Data Streams, and Amazon DynamoDB Streams.

Key Features

• Reports batch item failures to reduce number of retries for a record upon errors
• Simple interface to process each batch record
• Build your own batch processor by extending primitives

Problem Statement

When using SQS, Kinesis Data Streams, or DynamoDB Streams as a Lambda event source, your Lambda functions are triggered with a batch of messages.

If your function fails to process any message from the batch, the entire batch returns to your queue or stream. This same batch is then retried until either condition happens first: a) your Lambda function returns a successful response, b) record reaches maximum retry attempts, or c) when records expire.

With this utility, batch records are processed individually – only messages that failed to be processed return to the queue or stream for a further retry.

Getting Started

To get started, install the utility by running:

npm install @aws-lambda-powertools/batch

Then, define a record handler function:

This function will be called by the Batch Processing utility for each record in the batch. If the function throws an error, the record will be marked as failed and reported once the main handler returns.

Record handlers can be both synchronous and asynchronous, in the latter case the utility will process all the records of your batch in concurrently. To learn more about when it's safe to use async handlers, check the dedicated section in our docs.

SQS Processor

When using SQS as a Lambda event source, you can specify the EventType.SQS to process the records. The response will be a SQSBatchResponse which contains a list of items that failed to be processed.

To learn more about this mode, as well as how to process SQS FIFO queues, check the docs.

... (truncated)

Changelog

Sourced from @​aws-lambda-powertools/logger's changelog.

1.12.1 (2023-07-25)

Note: Version bump only for package aws-lambda-powertools-typescript

1.12.0 (2023-07-25)

Features

• batch: add batch processing utility (#1625) (c4e6b19), closes #1588 #1591 #1593 #1592 #1594
• logger: add cause to formatted error (#1617) (6a14595)

1.11.1 (2023-07-11)

Bug Fixes

• docs: fix alias in versions.json (#1576) (7198cbc)
• idempotency: types, docs, and makeIdempotent function wrapper (#1579) (bba1c01)

1.11.0 (2023-06-29)

Features

• idempotency: preserve original error when wrapping into IdempotencyPersistenceLayerError (#1552) (866837d)

Commits

• 2aa1d88 chore(release): v1.12.1 [skip ci]
• c303a59 chore(ci): add batch to build (#1630)
• e7d8411 chore: update layer ARN on documentation
• 368bb0d chore(release): v1.12.0 [skip ci]
• ee0a141 chore(commons): bump version prior to release (#1628)
• 02cd84b docs(parameters): add parameters examples cdk and sam (#1622)
• c4e6b19 feat(batch): add batch processing utility (#1625)
• 0b575a1 chore(maintenance): bump word-wrap from 1.2.3 to 1.2.4 (#1618)
• 6a14595 feat(logger): add cause to formatted error (#1617)
• a57dc11 chore(ci): restore dependencies & fix e2e tests (#1615)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually