Bump @aws-lambda-powertools/logger from 1.14.0 to 1.18.0 in /source/image-handler

[dependabot]

Bumps @aws-lambda-powertools/logger from 1.14.0 to 1.18.0.

Release notes

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

v1.18.0

Summary

This minor release introduces improvements around how the Idempotency utility handles conditional writes when used with DynamoDB as persistence layer. Additionally the release fixes an issue with expired AppConfig session tokens that affected long lived execution environments.

Idempotency: DynamoDB storage optimization

The Idempotency utility uses conditional writes to persist the idempotency state of a request. A failed conditional write signals to the utility that the request payload being processed has already been tried or is currently being processed.

Previously, condition check errors in single write operations did not return a copy of the item in the event of a condition check error. A separate read request was necessary to get the item and investigate the cause of the error.

Now that AWS introduced the ability to return a copy of the item as it was during the write attempt the Idempotency utility simplifies and lowers the cost of handling retries by removing the need to perform a separate read operation to retrieve the idempotency record of the request already processed.

Note that this feature requires you to use version v3.363.0 of the @aws-sdk/client-dynamodb or newer together with @aws-lambda-powertools/idempotency.

Parameters: AppConfig Session Token handling

When retrieving a configuration from AppConfig the Parameters utility retrieves a session token that can be used to retrieve the next value within 24 hours. Prior to this release the utility mistakenly assumed that the execution environment would be recycled before that time due to the Lambda timeout of 15 minutes.

For those customers who use provisioned concurrency or use the Parameters utility outside of Lambda however this was an issue as it caused the utility to fail retrieving new configurations from AppConfig due to an expired token. Starting from this release the utility keeps track of the token expiration timestamp and retrieves a new one before attempting to call AppConfig if the token has already expired.

Acknowledgements

Congrats to @​daschaa, @​tolutheo, and @​yamatatsu for getting their first PR merged 🎉

Changes

• chore(maintenance): add overwrite to artifact arn in layer pipeline (#1970) by @​dreamorosi
• chore(maintenance): group CDK cli with other CDK dependencies (#1968) by @​dreamorosi
• chore(maintenance): add environment scope to npm token (#1957) by @​dreamorosi
• chore(maintenance): fine tune dependabot config (#1935) by @​dreamorosi
• chore(ci): add aws-sdk group and ignore middy upgrades in examples (#1893) by @​am29d
• chore(ci): allow deps-dev for semantic PR (#1861) by @​am29d
• chore(ci): allow dependabot PRs (#1860) by @​heitorlessa
• chore(ci): [StepSecurity] Apply security best practices (#1839) by @​step-security-bot
• chore(internal): broken link in boring-cyborg app (#1807) by @​daschaa
• chore(ci): Update log retention for layers (#1809) by @​sthulb
• chore(ci): Update permissions in workflows (#1810) by @​sthulb
• chore(ci): sets base permissions on all workflows (#1801) by @​sthulb

🌟New features and non-breaking changes

• feat(idempotency): leverage new dynamodB Failed conditional writes behavior (#1779) by @​tolutheo

📜 Documentation updates

• chore(docs): bump layer version to 28 in docs (#1969) by @​am29d
• chore(docs): add link to performance tuning demo (#1960) by @​dreamorosi
• chore(layers): add ca-west-1 (#1836) by @​am29d
• feat(idempotency): leverage new dynamodB Failed conditional writes behavior (#1779) by @​tolutheo

... (truncated)

Changelog

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

Change Log

All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

1.16.1 (2023-11-24)

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

1.16.0 (2023-11-16)

Features

• logger: add support for AWS_LAMBDA_LOG_LEVEL and POWERTOOLS_LOG_LEVEL (#1795) (e69abfb)

1.15.0 (2023-11-14)

Features

• maintenance: add support for nodejs20.x runtime (#1790) (6b9b1bc)
• metrics: log directly to stdout (#1786) (75dc5b1)

1.14.2 (2023-11-03)

Bug Fixes

• metrics: deduplicate dimensions when serialising (#1780) (8181b48)

1.14.1 (2023-10-31)

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

Commits

• 7715df8 chore(release): v1.18.0 [skip ci]
• 76fc20c chore(docs): add link to performance tuning demo (#1960)
• a9e5ba6 chore(deps): bump the aws-sdk group with 9 updates (#1959)
• 32a477a chore(deps-dev): bump aws-sdk from 2.1540.0 to 2.1543.0 (#1958)
• 53976f9 chore(deps-dev): bump @​typescript-eslint/eslint-plugin (#1948)
• 481de73 chore(deps-dev): bump @​typescript-eslint/parser from 6.19.0 to 6.19.1 (#1946)
• 6a4213b chore(deps): bump actions/upload-artifact from 4.2.0 to 4.3.0 (#1950)
• 9fa7724 chore(deps): bump esbuild from 0.19.11 to 0.19.12 (#1952)
• 8c7286e chore(maintenance): add environment scope to npm token (#1957)
• c411407 chore(deps): bump mkdocs-material from 9.5.4 to 9.5.5 in /docs (#1949)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by aws-powertools-bot, a new releaser for @​aws-lambda-powertools/logger since your current version.

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 <dependency name> 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]

Superseded by #371.