chore(deps): bump aws-lambda-powertools from 1.11.0 to 1.12.0 in /lambda/src

[dependabot]

Bumps aws-lambda-powertools from 1.11.0 to 1.12.0.

Release notes

Sourced from aws-lambda-powertools's releases.

v1.12.0

Changes

This release brings a number of minor but importance enhancements in Logger, Parameters, Data Classes, Idempotency.

Also, this release wouldn't have been possible without @​michaelbrewer relentless contribution - Thank you, Michael!!

Logger

You can now inject correlation IDs coming from any Event Source using JMESPath expressions, or by manually injecting a string with set_correltion_id.

Another enhancement that goes nicely with any Logging Analytics solution such as Amazon CloudWatch Logs Insights, Kibana, Datadog, Splunk, Loggly, etc is the ability to enumerate exceptions across all your functions - A new field exception_name will be added to your Logs when using logger.exception().

Data Classes

You can now have a self-documented schema for AppSync Lambda Resolvers whether you use Direct Lambda Resolver feature, or @function GraphQL Transformer with Amplify CLI. More importantly, scalar type utilities such as timestamps, timezone offsets, UUIDs, are also available!

Another enhancement is additional documentation for Cognito custom auth challenges.

Parameters

A minor enhancement but important for sensitive parameters that cannot be cached. You can now use force_fetch=True parameter to always fetch the latest from your preferred parameter provider be that Parameter Store, Secrets Manager, AppConfig, DynamoDB, or your own.

We have also refreshed Parameters documentation using the new Getting started vs Advanced, including surfacing how you can control in-memory cache TTL for parameters retrieved.

Idempotency

Besides error handling improvements, thanks to @​dunedan and @​michaelbrewer (#318), you can now reuse a single DynamoDB table to store idempotency state. All new idempotency states stored in your DynamoDB table, as part of this release, will now contain your function name as a prefix for the hash key.

This is one step forward towards GA for Idempotency - The last missing feature before it's GA is allowing an exception callback mechanism so you can handle any exceptions to more easily return custom responses for event sources like API Gateway, AppSync, etc.

🌟New features and non-breaking changes

• feat(parameters): Add force_fetch option (#341) by @​michaelbrewer
• feat(data-classes): Add appsync scalar_types_utils and add support for timezone offsets (#339) by @​michaelbrewer
• feat(idempotent): Include function name in the idempotent key (#326) by @​michaelbrewer
• feat(data-classes): AppSync Resolver Event (#323) by @​michaelbrewer
• feat(logging): Add correlation_id support (#321) by @​michaelbrewer
• feat(logging): Include exception_name (#320) by @​michaelbrewer

📜 Documentation updates

• docs: surface new 1.12.0 features and enhancements (#344) by @​heitorlessa
• docs(data-classes): Add more cognito code examples (#340) by @​michaelbrewer

... (truncated)

Changelog

Sourced from aws-lambda-powertools's changelog.

[1.12.0] - 2021-03-17

Added

• Parameters: New force_fetch param to always fetch the latest and bypass cache, if available
• Data Classes: New AppSync Lambda Resolver event covering both Direct Lambda Resolver and Amplify GraphQL Transformer Resolver @function
• Data Classes: New AppSync scalar utilities to easily compose Lambda Resolvers with date utils, uuid, etc.
• Logger: Support for Correlation ID both in inject_lambda_context decorator and set_correlation_id method
• Logger: Include new exception_name key to help customers easily enumerate exceptions across all functions

Fixed

• Tracer: Type hint on return instance that made PyCharm no longer recognize autocompletion
• Idempotency: Error handling for missing idempotency key and save_in_progress errors

Commits

• 590fa3c chore: bump to 1.12.0
• d93be1c docs(tracer): Fix Tracer typing hinting for Pycharm (#345)
• 4c55108 docs: surface new 1.12.0 features and enhancements (#344)
• b365fba feat(parameters): Add force_fetch option (#341)
• 33bb7c8 docs(data-classes): Add more cognito code examples (#340)
• 542eb5b feat(data-classes): Add appsync scalar_types_utils (#339)
• 5daa45a feat(idempotent): Include function name in the idempotent key (#326)
• 34c2fa9 feat(data-classes): AppSync Resolver Event (#323)
• 6a9a554 chore: remove auto-label as restrictions prevent it from working
• 48a64eb feat(logging): Add correlation_id support (#321)
• 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)