chore(deps): bump aws-lambda-powertools from 2.14.1 to 2.15.0 in /lambda/src

[dependabot]

Bumps aws-lambda-powertools from 2.14.1 to 2.15.0.

Release notes

Sourced from aws-lambda-powertools's releases.

v2.15.0

Summary

This release is packed with a number of improvements:

• New external provider formats in Logger
• New Parser models and JMESPath expressions to naturally process S3 Event Notifications targets
• Printing Event Source Data Classes now automatically mask sensitive data
• New flush_metrics in Metrics to support customers using Lambda Web Adapter
• Added support for the China and GovCloud regions in API Gateway Authorizer event (bugfix)

And… a ton of documentation improvements.

⭐ Huge thanks to new contributors: @​theipster (S3 events), @​neilramsay (Data Class debug), @​arjanschaaf (Batch docs) and @​leif-ye (API Gateway Event Source)

External provider formats in the Logger utility

Docs: Observability providers

You can now send logs to the observability provider of your choice via Lambda Extensions. In most cases, you shouldn't need any custom Logger configuration, and logs will be shipped asynchronously with no performance impact.

Improved S3 Event Notifications developer experience

Docs: Built-in envelopes, Parser

S3 event notifications can be sometimes be ingested into Lambda via an intermediary such as an SQS queue (i.e. Lambda event source), for various architectural reasons - batching, retries, etc. However, from the Lambda function's perspective, the intermediary might not be too important; what's important is the S3 event notification itself. Now you can easily parse and access the inner payload for SQS-wrapper S3 events.

JMESPath

Parser

Printing Event Source Data Classes

Docs: Debugging

You can now print out the fields of a data class instance to obtain more information. All classes come with a __str__ method that generates a dictionary string which can be quite useful for debugging. Sensitive fields such as secret_access_key and session_token, are labeled as [SENSITIVE], to prevent any accidental disclosure of confidential information.

Flushing metrics manually

Docs: Flushing metrics manually

You can now manually flush the metrics at any time. This is useful when not running within a standard Lambda handler (e.g: Lambda Web Adapter), where the @log_metrics decorator does not work as intended.

... (truncated)

Changelog

Sourced from aws-lambda-powertools's changelog.

[v2.15.0] - 2023-05-04

Bug Fixes

• typo
• ci: pypi publishing was targetting test endpoint

Documentation

• batch: fixed typo in DynamoDB Streams section (#2189)
• examples: standardize lambda handler function name (#2192)
• homepage: add customer references section (#2159)
• jmespath: fix MD037/no-space-in-emphasis
• tutorial: use newer sam cli template; update to py3.10 (#2167)
• we-made-this: add serverless transactional message app (#2182)

Features

• ci: dispatch GitHub analytics action (#2161)
• event_source: support custom json_deserializer; add json_body in SQSEvent (#2200)
• event_source: add support for dynamic partitions in the Api Gateway Authorizer event (#2176)
• event_sources: Add str to Data Classes base DictWrapper (#2129)
• jmespath: new built-in envelopes to unwrap S3 events (#2169)
• logger: add DatadogLogFormatter and observability provider (#2183)
• metrics: add flush_metrics() method to allow manual flushing of metrics (#2171)
• parser: add support for SQS-wrapped S3 event notifications (#2108)

Maintenance

• update v2 layer ARN on documentation
• add dummy reusable dispatch analytics job
• ci: remove build step from release env; no more secrets need
• ci: use new pypi trusted publisher for increase security (#2198)
• deps: bump pypa/gh-action-pypi-publish from 1.8.5 to 1.8.6 (#2201)
• deps-dev: bump cfn-lint from 0.77.3 to 0.77.4 (#2178)
• deps-dev: bump types-requests from 2.28.11.17 to 2.29.0.0 (#2187)
• deps-dev: bump coverage from 7.2.4 to 7.2.5 (#2186)
• deps-dev: bump mkdocs-material from 9.1.8 to 9.1.9 (#2190)
• deps-dev: bump importlib-metadata from 6.5.0 to 6.6.0 (#2163)
• deps-dev: bump mypy-boto3-xray from 1.26.11.post1 to 1.26.122 (#2173)
• deps-dev: bump aws-cdk from 2.76.0 to 2.77.0 (#2174)
• deps-dev: bump mypy-boto3-lambda from 1.26.115 to 1.26.122 (#2172)
• deps-dev: bump cfn-lint from 0.77.2 to 0.77.3 (#2165)
• deps-dev: bump mkdocs-material from 9.1.6 to 9.1.8 (#2162)
• deps-dev: bump coverage from 7.2.3 to 7.2.4 (#2179)
• governance: add Lambda Powertools for .NET in issue templates (#2196)

Commits

• 9594b86 chore: update v2 layer ARN on documentation
• 409cb65 chore(ci): remove build step from release env; no more secrets need
• ae7ae93 update changelog with latest changes
• 7504eb0 fix(ci): pypi publishing was targetting test endpoint
• 83024f8 bump version to 2.15.0
• 3660dbf feat(event_source): support custom json_deserializer; add json_body in SQSEve...
• fff75bd chore(deps): bump pypa/gh-action-pypi-publish from 1.8.5 to 1.8.6 (#2201)
• 538f12d chore(ci): use new pypi trusted publisher for increase security (#2198)
• 58e63b5 update changelog with latest changes
• 68c8562 docs(examples): standardize lambda handler function name (#2192)
• 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 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)