search

aws-samples / aws-control-tower-org-setup-sample

Automated AWS Organizations configuration for security operations
https://aws.amazon.com/controltower/
MIT No Attribution
34 stars 12 forks source link

chore(deps): bump aws-lambda-powertools[aws-sdk] from 2.30.2 to 2.32.0 #22

Closed dependabot[bot] closed 9 months ago

dependabot[bot] commented 9 months ago

Bumps aws-lambda-powertools[aws-sdk] from 2.30.2 to 2.32.0.

Release notes

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

v2.32.0

Summary

We're excited to introduce two significant new features in our Idempotency utility:

  • Support for Redis as an Idempotency persistent storage layer
  • DynamoDB storage layer is now faster and cheaper by leveraging conditional writes

We also made enhancements to our OpenAPI and Event Sources utilities, and fixed some bugs!

⭐ Huge thanks to our new contributors: @​sbailliez, @​Thomas-McKanna, and @​dastra!

Redis as an Idempotency persistent storage layer

Docs

You can now seamlessly switch between DynamoDB and Redis as a persistence storage layer. This allows you to leverage the Idempotency utility in previously unavailable scenarios, such as handling responses over 400kb.

We remain committed to making efforts to introduce new backends, and we would love to hear from you on which backend we should prioritize next!

redis_idempotency2

⭐ ⭐ Huge thanks to @​roger-zhangg for your help!

Optimized DynamoDB storage layer with conditional writes

AWS has recently introduced support for ReturnValuesOnConditionCheckFailure, a feature designed to streamline conditional write operations and reducing costs in Amazon DynamoDB. With this enhancement, Powertools for AWS Lambda now optimistically attempts to write items to DynamoDB. If the item already exists, it seamlessly returns it from DynamoDB without requiring an additional operation.

S3 Batch Operations Event Source

Docs

S3 Batch Operations are now supported on the Event Source utility. When using S3 Batch Operations, a Lambda function can be used to execute various operations. For each task, you can choose to either:

A) Return the task as a success (default) B) Return the task as temporarily failed (e.g., due to a timeout when connecting to other services) and enable automatic retries. C) Return the task as permanently failed, resulting in job failure.

This example illustrates how you can return different status based on your specific execution logic.

s3_batch2

OpenAPI response models

Docs

You can now define additional response models within the OpenAPI schema utility, allowing you to leverage existing Pydantic data models and classes.

response

... (truncated)

Changelog

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

[v2.32.0] - 2024-01-19

Bug Fixes

  • event_handler: escape OpenAPI schema on Swagger UI (#3606)

Code Refactoring

  • event-handler: Inject CSS and JS files into SwaggerUI route when no custom CDN is used. (#3562)
  • event_handler: fix BedrockAgentResolver docstring (#3645)

Documentation

  • homepage: add banner about Python 3.7 deprecation (#3618)
  • i-made-this: added new article on how to create a serverless API with CDK and Powertools (#3605)

Features

  • event_handler: add support for additional response models (#3591)
  • event_handler: add support to download OpenAPI spec file (#3571)
  • event_source: Add support for S3 batch operations (#3572)
  • event_source: Add support for policyLevel field in CloudWatch Logs event and parser (#3624)
  • idempotency: leverage new DynamoDB Failed conditional writes behavior with ReturnValuesOnConditionCheckFailure (#3446)
  • idempotency: adding redis as idempotency backend (#2567)

Maintenance

  • version bump
  • ci: Disable Redis e2e until we drop Python 3.7 (#3652)
  • ci: update boto3 library version to 1.26.164+ (#3632)
  • deps: bump the layer-balancer group in /layer/scripts/layer-balancer with 1 update (#3649)
  • deps: bump jinja2 from 3.1.2 to 3.1.3 in /docs (#3620)
  • deps: bump the layer-balancer group in /layer/scripts/layer-balancer with 1 update (#3639)
  • deps: bump gitpython from 3.1.37 to 3.1.41 in /docs (#3610)
  • deps: bump squidfunk/mkdocs-material from 2f29d71 to 58eef6c in /docs (#3633)
  • deps: bump redis from 4.6.0 to 5.0.1 (#3613)
  • deps-dev: bump gitpython from 3.1.40 to 3.1.41 (#3611)
  • deps-dev: bump sentry-sdk from 1.39.1 to 1.39.2 (#3614)
  • deps-dev: bump aws-cdk from 2.120.0 to 2.121.1 (#3634)
  • deps-dev: bump jinja2 from 3.1.2 to 3.1.3 (#3619)
  • deps-dev: bump cfn-lint from 0.83.7 to 0.83.8 (#3603)
  • deps-dev: bump aws-cdk from 2.121.1 to 2.122.0 (#3648)
  • deps-dev: bump ruff from 0.1.11 to 0.1.13 (#3625)
  • deps-dev: bump aws-cdk from 2.118.0 to 2.120.0 (#3627)

[v2.31.0] - 2024-01-05

Bug Fixes

  • ci: fail dispatch analytics job when Lambda call fails (#3579)

... (truncated)

Commits
  • 7bb9f68 chore: version bump
  • f833233 feat(idempotency): leverage new DynamoDB Failed conditional writes behavior w...
  • 79e248c chore(ci): Disable Redis e2e until we drop Python 3.7 (#3652)
  • 2a4ec52 chore(ci): changelog rebuild (#3650)
  • 138fe8c chore(deps): bump the layer-balancer group in /layer/scripts/layer-balancer w...
  • 1327a74 chore(deps-dev): bump aws-cdk from 2.121.1 to 2.122.0 (#3648)
  • 3c63c24 refactor(event_handler): fix BedrockAgentResolver docstring (#3645)
  • c8958c8 chore(ci): changelog rebuild (#3643)
  • c466c80 feat(event_source): Add support for S3 batch operations (#3572)
  • 9afbc78 chore(ci): changelog rebuild (#3641)
  • Additional commits viewable in compare view


Dependabot compatibility score

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)