From e18ac600bbad9df67a1ea02a1155044bfb44cef4 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Thu, 17 Oct 2024 09:21:59 +0200 Subject: [PATCH] fix(lambda): bump the aws-powertools group in /lambdas with 4 updates (#4184) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bumps the aws-powertools group in /lambdas with 4 updates: [@aws-lambda-powertools/parameters](https://github.com/aws-powertools/powertools-lambda-typescript), [@aws-lambda-powertools/logger](https://github.com/aws-powertools/powertools-lambda-typescript), [@aws-lambda-powertools/metrics](https://github.com/aws-powertools/powertools-lambda-typescript) and [@aws-lambda-powertools/tracer](https://github.com/aws-powertools/powertools-lambda-typescript). Updates `@aws-lambda-powertools/parameters` from 2.8.0 to 2.9.0
Release notes

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

v2.9.0

Summary

This release introduces 1/ the ability to process records sequentially when working with async functions in Batch Processing, 2/ a new option for Idempotency to manipulate the payload stored for idempotent operations, and 3/ the option to specify custom JMESPath functions when selecting an idempotency key.

Finally, you can now use the Parser utility when using our public AWS Lambda layers.

⭐️ Thanks to @​arnabrahman, @​garysassano and, @​scratchclaggy for their big contributions to this release!

Sequential async processing

Docs

You can now process records sequentially when working with async functions in Batch Processing by setting the processInParallel option to false. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.

carbon-4

Manipulating idempotent responses

Docs

Now you can set up a responseHook function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.

carbon-3

Custom JMESPath functions with Idempotency

Docs

You can now use custom JMESPath functions with the Idempotency utility by configuring the jmesPathOptions in your idempotency configuration. This is useful when you’re making idempotent operations that accept complex payloads or encoding formats that are not supported by default.

carbon-4

Changes

🌟New features and non-breaking changes

... (truncated)

Changelog

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

2.9.0 (2024-10-07)

Features

Commits

Updates `@aws-lambda-powertools/logger` from 2.8.0 to 2.9.0
Release notes

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

v2.9.0

Summary

This release introduces 1/ the ability to process records sequentially when working with async functions in Batch Processing, 2/ a new option for Idempotency to manipulate the payload stored for idempotent operations, and 3/ the option to specify custom JMESPath functions when selecting an idempotency key.

Finally, you can now use the Parser utility when using our public AWS Lambda layers.

⭐️ Thanks to @​arnabrahman, @​garysassano and, @​scratchclaggy for their big contributions to this release!

Sequential async processing

Docs

You can now process records sequentially when working with async functions in Batch Processing by setting the processInParallel option to false. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.

carbon-4

Manipulating idempotent responses

Docs

Now you can set up a responseHook function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.

carbon-3

Custom JMESPath functions with Idempotency

Docs

You can now use custom JMESPath functions with the Idempotency utility by configuring the jmesPathOptions in your idempotency configuration. This is useful when you’re making idempotent operations that accept complex payloads or encoding formats that are not supported by default.

carbon-4

Changes

🌟New features and non-breaking changes

... (truncated)

Changelog

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

2.9.0 (2024-10-07)

Features

Commits

Updates `@aws-lambda-powertools/metrics` from 2.8.0 to 2.9.0
Release notes

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

v2.9.0

Summary

This release introduces 1/ the ability to process records sequentially when working with async functions in Batch Processing, 2/ a new option for Idempotency to manipulate the payload stored for idempotent operations, and 3/ the option to specify custom JMESPath functions when selecting an idempotency key.

Finally, you can now use the Parser utility when using our public AWS Lambda layers.

⭐️ Thanks to @​arnabrahman, @​garysassano and, @​scratchclaggy for their big contributions to this release!

Sequential async processing

Docs

You can now process records sequentially when working with async functions in Batch Processing by setting the processInParallel option to false. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.

carbon-4

Manipulating idempotent responses

Docs

Now you can set up a responseHook function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.

carbon-3

Custom JMESPath functions with Idempotency

Docs

You can now use custom JMESPath functions with the Idempotency utility by configuring the jmesPathOptions in your idempotency configuration. This is useful when you’re making idempotent operations that accept complex payloads or encoding formats that are not supported by default.

carbon-4

Changes

🌟New features and non-breaking changes

... (truncated)

Changelog

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

2.9.0 (2024-10-07)

Features

Commits

Updates `@aws-lambda-powertools/tracer` from 2.8.0 to 2.9.0
Release notes

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

v2.9.0

Summary

This release introduces 1/ the ability to process records sequentially when working with async functions in Batch Processing, 2/ a new option for Idempotency to manipulate the payload stored for idempotent operations, and 3/ the option to specify custom JMESPath functions when selecting an idempotency key.

Finally, you can now use the Parser utility when using our public AWS Lambda layers.

⭐️ Thanks to @​arnabrahman, @​garysassano and, @​scratchclaggy for their big contributions to this release!

Sequential async processing

Docs

You can now process records sequentially when working with async functions in Batch Processing by setting the processInParallel option to false. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.

carbon-4

Manipulating idempotent responses

Docs

Now you can set up a responseHook function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.

carbon-3

Custom JMESPath functions with Idempotency

Docs

You can now use custom JMESPath functions with the Idempotency utility by configuring the jmesPathOptions in your idempotency configuration. This is useful when you’re making idempotent operations that accept complex payloads or encoding formats that are not supported by default.

carbon-4

Changes

🌟New features and non-breaking changes

... (truncated)

Changelog

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

2.9.0 (2024-10-07)

Features

Commits

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-automerge-start) [//]: # (dependabot-automerge-end) ---
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 major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- lambdas/functions/control-plane/package.json | 2 +- lambdas/libs/aws-powertools-util/package.json | 6 +- lambdas/yarn.lock | 66 +++++++++---------- 3 files changed, 37 insertions(+), 37 deletions(-) diff --git a/lambdas/functions/control-plane/package.json b/lambdas/functions/control-plane/package.json index 3c433df35e..7095eab962 100644 --- a/lambdas/functions/control-plane/package.json +++ b/lambdas/functions/control-plane/package.json @@ -40,7 +40,7 @@ "dependencies": { "@aws-github-runner/aws-powertools-util": "*", "@aws-github-runner/aws-ssm-util": "*", - "@aws-lambda-powertools/parameters": "^2.8.0", + "@aws-lambda-powertools/parameters": "^2.9.0", "@aws-sdk/client-ec2": "^3.666.0", "@aws-sdk/client-sqs": "^3.666.0", "@aws-sdk/types": "^3.664.0", diff --git a/lambdas/libs/aws-powertools-util/package.json b/lambdas/libs/aws-powertools-util/package.json index ca12d8573d..db9c512a8c 100644 --- a/lambdas/libs/aws-powertools-util/package.json +++ b/lambdas/libs/aws-powertools-util/package.json @@ -35,9 +35,9 @@ "typescript": "^5.5.4" }, "dependencies": { - "@aws-lambda-powertools/logger": "^2.8.0", - "@aws-lambda-powertools/metrics": "^2.8.0", - "@aws-lambda-powertools/tracer": "^2.8.0", + "@aws-lambda-powertools/logger": "^2.9.0", + "@aws-lambda-powertools/metrics": "^2.9.0", + "@aws-lambda-powertools/tracer": "^2.9.0", "aws-lambda": "^1.0.7" }, "nx": { diff --git a/lambdas/yarn.lock b/lambdas/yarn.lock index db608de457..9167b4d69e 100644 --- a/lambdas/yarn.lock +++ b/lambdas/yarn.lock @@ -134,9 +134,9 @@ __metadata: version: 0.0.0-use.local resolution: "@aws-github-runner/aws-powertools-util@workspace:libs/aws-powertools-util" dependencies: - "@aws-lambda-powertools/logger": "npm:^2.8.0" - "@aws-lambda-powertools/metrics": "npm:^2.8.0" - "@aws-lambda-powertools/tracer": "npm:^2.8.0" + "@aws-lambda-powertools/logger": "npm:^2.9.0" + "@aws-lambda-powertools/metrics": "npm:^2.9.0" + "@aws-lambda-powertools/tracer": "npm:^2.9.0" "@trivago/prettier-plugin-sort-imports": "npm:^4.3.0" "@types/aws-lambda": "npm:^8.10.145" "@types/express": "npm:^4.17.21" @@ -195,7 +195,7 @@ __metadata: dependencies: "@aws-github-runner/aws-powertools-util": "npm:*" "@aws-github-runner/aws-ssm-util": "npm:*" - "@aws-lambda-powertools/parameters": "npm:^2.8.0" + "@aws-lambda-powertools/parameters": "npm:^2.9.0" "@aws-sdk/client-ec2": "npm:^3.666.0" "@aws-sdk/client-sqs": "npm:^3.666.0" "@aws-sdk/types": "npm:^3.664.0" @@ -327,47 +327,47 @@ __metadata: languageName: unknown linkType: soft -"@aws-lambda-powertools/commons@npm:^2.8.0": - version: 2.8.0 - resolution: "@aws-lambda-powertools/commons@npm:2.8.0" - checksum: 10c0/d8e5591e4bf56f3aaaa3015a78f5a3c7db84ff81e9b709d3317e7b79909ac34873c9533236dca829b45aae1cc87ad8519cfa3606dc3db8ac993ffa24ecd20b1a +"@aws-lambda-powertools/commons@npm:^2.9.0": + version: 2.9.0 + resolution: "@aws-lambda-powertools/commons@npm:2.9.0" + checksum: 10c0/93754305c05196651dce62c68a8ceb5fe59e029fe11f1361a06d192e34cee07e70f9cc0e17eefaa4a760f3910eb02f2f0b70cb9482d3635e05afe217a2ee1766 languageName: node linkType: hard -"@aws-lambda-powertools/logger@npm:^2.8.0": - version: 2.8.0 - resolution: "@aws-lambda-powertools/logger@npm:2.8.0" +"@aws-lambda-powertools/logger@npm:^2.9.0": + version: 2.9.0 + resolution: "@aws-lambda-powertools/logger@npm:2.9.0" dependencies: - "@aws-lambda-powertools/commons": "npm:^2.8.0" + "@aws-lambda-powertools/commons": "npm:^2.9.0" lodash.merge: "npm:^4.6.2" peerDependencies: "@middy/core": 4.x || 5.x peerDependenciesMeta: "@middy/core": optional: true - checksum: 10c0/464d05a2f81b5802956efa7eaac2c6a1d42edd9c78181d4e67de09ee01efe78caa5644e5517308fb67ded23dd8eb51ac282327755ab3e2c7672ec1fb26d7e5a0 + checksum: 10c0/5afb0a2a77bb23eb7c18fd96e46f7bafccd7ed616bd18c4e023a1af556c566ede8c92ba5285ec5f8cdb9ebfe73055903ee25b595642b5d7ebbb1ab8b28658640 languageName: node linkType: hard -"@aws-lambda-powertools/metrics@npm:^2.8.0": - version: 2.8.0 - resolution: "@aws-lambda-powertools/metrics@npm:2.8.0" +"@aws-lambda-powertools/metrics@npm:^2.9.0": + version: 2.9.0 + resolution: "@aws-lambda-powertools/metrics@npm:2.9.0" dependencies: - "@aws-lambda-powertools/commons": "npm:^2.8.0" + "@aws-lambda-powertools/commons": "npm:^2.9.0" peerDependencies: "@middy/core": 4.x || 5.x peerDependenciesMeta: "@middy/core": optional: true - checksum: 10c0/7deb11c757a77f4cca76cf212bcc648340a6dd6a52ec93f1693024280876938d62328e2ed512d94d2e5a374956bda8a3600c94826606ba78f6dbf73a59dde5b5 + checksum: 10c0/bc6e3c57be24d77cc770ba93903a8fce050b34080e4de3b8432ccfb601da6d097730008d2b2203e391c9782fc8a05c504ef9b37adb78d589a2a83dbb2f418878 languageName: node linkType: hard -"@aws-lambda-powertools/parameters@npm:^2.8.0": - version: 2.8.0 - resolution: "@aws-lambda-powertools/parameters@npm:2.8.0" +"@aws-lambda-powertools/parameters@npm:^2.9.0": + version: 2.9.0 + resolution: "@aws-lambda-powertools/parameters@npm:2.9.0" dependencies: - "@aws-lambda-powertools/commons": "npm:^2.8.0" + "@aws-lambda-powertools/commons": "npm:^2.9.0" peerDependencies: "@aws-sdk/client-appconfigdata": ">=3.x" "@aws-sdk/client-dynamodb": ">=3.x" @@ -388,22 +388,22 @@ __metadata: optional: true "@middy/core": optional: true - checksum: 10c0/f44146f80a5ad771e0f46411b5ddf9cd72852d60491e0929e2c4546222186758716aab3a7a71b67d151b02d380033ca8eacf78f81a4b29dd95d1bc977fc8622a + checksum: 10c0/551e6c70bab4263b83f6000f1dbe9ee4142f23a0514d6e5bca8066629c1b0d5e6e722456cb106c7ef6bd56c3ee87a896e88e3fdcb579a1bc070cb96806f054ca languageName: node linkType: hard -"@aws-lambda-powertools/tracer@npm:^2.8.0": - version: 2.8.0 - resolution: "@aws-lambda-powertools/tracer@npm:2.8.0" +"@aws-lambda-powertools/tracer@npm:^2.9.0": + version: 2.9.0 + resolution: "@aws-lambda-powertools/tracer@npm:2.9.0" dependencies: - "@aws-lambda-powertools/commons": "npm:^2.8.0" - aws-xray-sdk-core: "npm:^3.10.0" + "@aws-lambda-powertools/commons": "npm:^2.9.0" + aws-xray-sdk-core: "npm:^3.10.1" peerDependencies: "@middy/core": 4.x || 5.x peerDependenciesMeta: "@middy/core": optional: true - checksum: 10c0/2d781e5d60a905f5f829585605a9891b5f4cb8f952bf202c55ef61bb2d9f847a79787f7c3c18abf7614daa1d602aebc6c7bcbea5c6c01650da5a8cc03cd5d6b0 + checksum: 10c0/06eed6ee7c5aff687995c0442a8faf3e1e743167d2d65ba814f45d0eae1c12089b4040eb4032f9bb864451c45f8febcdc9a4588daafc16e363fbdfe3e6a235c6 languageName: node linkType: hard @@ -5806,9 +5806,9 @@ __metadata: languageName: node linkType: hard -"aws-xray-sdk-core@npm:^3.10.0": - version: 3.10.0 - resolution: "aws-xray-sdk-core@npm:3.10.0" +"aws-xray-sdk-core@npm:^3.10.1": + version: 3.10.1 + resolution: "aws-xray-sdk-core@npm:3.10.1" dependencies: "@aws-sdk/types": "npm:^3.4.1" "@smithy/service-error-classification": "npm:^2.0.4" @@ -5816,7 +5816,7 @@ __metadata: atomic-batcher: "npm:^1.0.2" cls-hooked: "npm:^4.2.2" semver: "npm:^7.5.3" - checksum: 10c0/4c8985d49974d1b880bda8d1ecea921c00200da7d5e491ab8c8a7dcaab21503ea14f1f20c22d86622531bb765ad4d4edf616d061d6f395f792d6426427a86e38 + checksum: 10c0/e7a084e08458ef8a75001ef5ddc137633d741f164e2e1126deae2065926e9d464ca494e55240193062503b32d512e567a2d7bc3f6ced8dff137a425d4623f0bb languageName: node linkType: hard