Bump aws-lambda-powertools[parser] from 2.36.0 to 2.41.0 in /apps/sps

[dependabot[bot]]

Bumps aws-lambda-powertools[parser] from 2.36.0 to 2.41.0.

Release notes

Sourced from aws-lambda-powertools[parser]'s releases.

v2.41.0

Summary

This release enhances the Batch Processing feature, which you can now customize to not throw an error when the entire batch of items fails to process.

We have also added three new Pydantic models to our Parser feature to work with authorizers in Amazon API Gateway.

Thanks to @​adriantomas, customers can bring their own boto3 client when using Feature Flags feature.

🌟 ⭐ A big thank you to everyone who helped make this release.

Working with full batch failures

Docs

You can now set the raise_on_entire_batch_failure option to False to prevent the Batch Processing utility from throwing a BatchProcessingError, when all records in a batch fail to process. This is useful when working with functions that handle batches with a small number of records, or when you use errors as a flow control mechanism.

New Parser models

Docs

You can now use the new Pydantic models to validate payloads originating from authorization events in REST and HTTP APIs.

Here are all the modules we've added:

• ApiGatewayAuthorizerToken - For REST API Authorizer events using Token
• ApiGatewayAuthorizerRequest - For REST API Authorizer events using Request
• ApiGatewayAuthorizerRequestV2 - For HTTP API Authorizer events using Request

Customizing boto3 client configuration for Feature Flags

Docs

You can now bring your own boto3 client instance when using Feature Flags. This is ideal when you want to reuse or customize the appconfigdata client.

Last but not least, thanks to @​Wurstnase for helping us to fix a bug when using CORS in the Event Handler feature.

Changes

🌟New features and non-breaking changes

• feat(feature_flags): allow customers to bring their own boto3 client and session (#4717) by @​adriantomas
• feat(batch): add option to not raise BatchProcessingError exception when the entire batch fails (#4719) by @​leandrodamascena

... (truncated)

Changelog

Sourced from aws-lambda-powertools[parser]'s changelog.

[v2.41.0] - 2024-07-11

Maintenance

• version bump
• layers: downgrade aws cdk to 2.145.0 (#4739)

[v2.40.1] - 2024-06-28

Bug Fixes

• event_handler: current_event regression AppSyncResolver Router (#4652)

Maintenance

• version bump
• ci: new pre-release 2.40.1a1 (#4653)
• ci: new pre-release 2.40.1a0 (#4648)
• deps-dev: bump cfn-lint from 1.3.7 to 1.4.1 (#4646)
• deps-dev: bump sentry-sdk from 2.7.0 to 2.7.1 (#4645)

[v2.40.0] - 2024-06-27

Bug Fixes

• event_sources: change partition and offset field types in KafkaEventRecord (#4515)

Documentation

• homepage: Fix homepage link (#4587)
• i-made-this: add new article about best practices for accelerating serverless development (#4518)
• public reference: add Brsk as a public reference (#4597)

Features

• event-handler: add appsync batch resolvers (#1998)
• validation: support JSON Schema referencing in validation utils (#4508)

Maintenance

• version bump
• ci: add the Metrics feature to nox tests (#4552)
• ci: new pre-release 2.39.2a5 (#4636)
• ci: add the Streaming feature to nox tests (#4575)
• ci: new pre-release 2.39.2a4 (#4629)
• ci: new pre-release 2.39.2a3 (#4620)
• ci: add the Event Handler feature to nox tests (#4581)
• ci: add the Data Class feature to nox tests (#4583)
• ci: add the Parser feature to nox tests (#4584)

... (truncated)

Commits

• 3556fcd chore: version bump
• 4e9a5fe chore(layers): downgrade aws cdk to 2.145.0 (#4739)
• b5d6384 chore(ci): new pre-release 2.40.2a8 (#4737)
• 3ae2eec fix(event_handler): make the max_age attribute comply with RFC specification ...
• 599f6fe chore(deps-dev): bump sentry-sdk from 2.8.0 to 2.9.0 (#4735)
• 96fd770 chore(deps-dev): bump cfn-lint from 1.5.2 to 1.5.3 (#4734)
• 2f4b976 chore(deps): bump actions/setup-python from 5.1.0 to 5.1.1 (#4732)
• 51de224 chore(deps): bump the layer-balancer group in /layer/scripts/layer-balancer w...
• 10d551c feat(feature_flags): allow customers to bring their own boto3 client and sess...
• 14b44ce feat(batch): add option to not raise BatchProcessingError exception when th...
• 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 - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

The following labels could not be found: dependencies.

[dependabot[bot]]

Superseded by #23.