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
You can now process records sequentially when working with async functions in Batch Processing by setting the
processInParallel
option tofalse
. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.Manipulating idempotent responses
Now you can set up a
responseHook
function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.Custom JMESPath functions with Idempotency
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.Changes
- chore(layers): remove schema parsing from layer canary (#3171) by
@dreamorosi
- chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions from 3.0.12 to 3.0.14 (#3162) by
@dependabot
- chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157) by
@dependabot
- chore(deps): bump actions/checkout from 4.1.7 to 4.2.0 (#3122) by
@dependabot
- chore(deps): bump github/codeql-action from 3.26.8 to 3.26.9 (#3114) by
@dependabot
- chore(deps): bump actions/setup-node from 4.0.3 to 4.0.4 (#3097) by
@dependabot
- chore(layers): add Parser to layer (#3101) by
@scratchclaggy
- chore(deps): bump github/codeql-action from 3.26.7 to 3.26.8 (#3087) by
@dependabot
🌟New features and non-breaking changes
- feat(idempotency): ability to specify JMESPath custom functions (#3150) by
@arnabrahman
- feat(batch): sequential async processing of records for
BatchProcessor
(#3109) by@arnabrahman
- feat(idempotency): manipulate idempotent response via response hook (#3071) by
@arnabrahman
... (truncated)
71e70f5
chore(ci): bump version to 2.9.0 (#3164)74c6edd
chore(deps): bump the aws-cdk group across 1 directory with 2 updates
(#3163)613d32c
chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions
from 3.0...39b805b
chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates
(#3156)7be70a1
chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157)489c8ad
chore(maintenance): add Flyweight customer reference (#3161)0c44517
docs(parser): highlight JSONStringify
helper (#3158)869b6fc
feat(idempotency): ability to specify JMESPath custom functions (#3150)686e524
chore(metrics): expose MetricsInterface
as return type of
single metric and...c97d379
test(idempotency): switch e2e tests to vitest (#3149)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
You can now process records sequentially when working with async functions in Batch Processing by setting the
processInParallel
option tofalse
. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.Manipulating idempotent responses
Now you can set up a
responseHook
function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.Custom JMESPath functions with Idempotency
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.Changes
- chore(layers): remove schema parsing from layer canary (#3171) by
@dreamorosi
- chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions from 3.0.12 to 3.0.14 (#3162) by
@dependabot
- chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157) by
@dependabot
- chore(deps): bump actions/checkout from 4.1.7 to 4.2.0 (#3122) by
@dependabot
- chore(deps): bump github/codeql-action from 3.26.8 to 3.26.9 (#3114) by
@dependabot
- chore(deps): bump actions/setup-node from 4.0.3 to 4.0.4 (#3097) by
@dependabot
- chore(layers): add Parser to layer (#3101) by
@scratchclaggy
- chore(deps): bump github/codeql-action from 3.26.7 to 3.26.8 (#3087) by
@dependabot
🌟New features and non-breaking changes
- feat(idempotency): ability to specify JMESPath custom functions (#3150) by
@arnabrahman
- feat(batch): sequential async processing of records for
BatchProcessor
(#3109) by@arnabrahman
- feat(idempotency): manipulate idempotent response via response hook (#3071) by
@arnabrahman
... (truncated)
71e70f5
chore(ci): bump version to 2.9.0 (#3164)74c6edd
chore(deps): bump the aws-cdk group across 1 directory with 2 updates
(#3163)613d32c
chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions
from 3.0...39b805b
chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates
(#3156)7be70a1
chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157)489c8ad
chore(maintenance): add Flyweight customer reference (#3161)0c44517
docs(parser): highlight JSONStringify
helper (#3158)869b6fc
feat(idempotency): ability to specify JMESPath custom functions (#3150)686e524
chore(metrics): expose MetricsInterface
as return type of
single metric and...c97d379
test(idempotency): switch e2e tests to vitest (#3149)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
You can now process records sequentially when working with async functions in Batch Processing by setting the
processInParallel
option tofalse
. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.Manipulating idempotent responses
Now you can set up a
responseHook
function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.Custom JMESPath functions with Idempotency
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.Changes
- chore(layers): remove schema parsing from layer canary (#3171) by
@dreamorosi
- chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions from 3.0.12 to 3.0.14 (#3162) by
@dependabot
- chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157) by
@dependabot
- chore(deps): bump actions/checkout from 4.1.7 to 4.2.0 (#3122) by
@dependabot
- chore(deps): bump github/codeql-action from 3.26.8 to 3.26.9 (#3114) by
@dependabot
- chore(deps): bump actions/setup-node from 4.0.3 to 4.0.4 (#3097) by
@dependabot
- chore(layers): add Parser to layer (#3101) by
@scratchclaggy
- chore(deps): bump github/codeql-action from 3.26.7 to 3.26.8 (#3087) by
@dependabot
🌟New features and non-breaking changes
- feat(idempotency): ability to specify JMESPath custom functions (#3150) by
@arnabrahman
- feat(batch): sequential async processing of records for
BatchProcessor
(#3109) by@arnabrahman
- feat(idempotency): manipulate idempotent response via response hook (#3071) by
@arnabrahman
... (truncated)
71e70f5
chore(ci): bump version to 2.9.0 (#3164)74c6edd
chore(deps): bump the aws-cdk group across 1 directory with 2 updates
(#3163)613d32c
chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions
from 3.0...39b805b
chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates
(#3156)7be70a1
chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157)489c8ad
chore(maintenance): add Flyweight customer reference (#3161)0c44517
docs(parser): highlight JSONStringify
helper (#3158)869b6fc
feat(idempotency): ability to specify JMESPath custom functions (#3150)686e524
chore(metrics): expose MetricsInterface
as return type of
single metric and...c97d379
test(idempotency): switch e2e tests to vitest (#3149)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
You can now process records sequentially when working with async functions in Batch Processing by setting the
processInParallel
option tofalse
. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.Manipulating idempotent responses
Now you can set up a
responseHook
function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.Custom JMESPath functions with Idempotency
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.Changes
- chore(layers): remove schema parsing from layer canary (#3171) by
@dreamorosi
- chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions from 3.0.12 to 3.0.14 (#3162) by
@dependabot
- chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157) by
@dependabot
- chore(deps): bump actions/checkout from 4.1.7 to 4.2.0 (#3122) by
@dependabot
- chore(deps): bump github/codeql-action from 3.26.8 to 3.26.9 (#3114) by
@dependabot
- chore(deps): bump actions/setup-node from 4.0.3 to 4.0.4 (#3097) by
@dependabot
- chore(layers): add Parser to layer (#3101) by
@scratchclaggy
- chore(deps): bump github/codeql-action from 3.26.7 to 3.26.8 (#3087) by
@dependabot
🌟New features and non-breaking changes
- feat(idempotency): ability to specify JMESPath custom functions (#3150) by
@arnabrahman
- feat(batch): sequential async processing of records for
BatchProcessor
(#3109) by@arnabrahman
- feat(idempotency): manipulate idempotent response via response hook (#3071) by
@arnabrahman
... (truncated)
71e70f5
chore(ci): bump version to 2.9.0 (#3164)74c6edd
chore(deps): bump the aws-cdk group across 1 directory with 2 updates
(#3163)613d32c
chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions
from 3.0...39b805b
chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates
(#3156)7be70a1
chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157)489c8ad
chore(maintenance): add Flyweight customer reference (#3161)0c44517
docs(parser): highlight JSONStringify
helper (#3158)869b6fc
feat(idempotency): ability to specify JMESPath custom functions (#3150)686e524
chore(metrics): expose MetricsInterface
as return type of
single metric and...c97d379
test(idempotency): switch e2e tests to vitest (#3149)