Closed hjgraca closed 4 months ago
Issues
3 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
2.0% Duplication on New Code
Attention: Patch coverage is 72.32741%
with 950 lines
in your changes are missing coverage. Please review.
Project coverage is 72.58%. Comparing base (
5bc87a0
) to head (c744870
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Description of your changes
This PR introduces support for Powertools internal JMESPath functions to the Idempotency utility. This PR will remove the 3rd party dependency of JMESPath.NET thus strengthening our project to supply chain attacks and 3rd party maintainers.
With this new feature customers can use the
powertools_json()
,powertools_base64()
, andpowertools_base64_gzip()
custom functions to deserialize encoded payloads and use the values within them as idempotency key.This is especially useful when working with API Gateway or SQS messages among others, since oftentimes the customer defined part of the payload is encoded as JSON stringified object or base64 encoded value:
The feature is added by having the Idempotency utility take a dependency on the new
AWS.Lambda.Powertools.JMESPath
project and replacing the existing,JMESPath.NET
external dependency.To be discussed if we should release
AWS.Lambda.Powertools.JMESPath
as a new NuGet package, so people can use it outside Idempotency utility.Related issues, RFCs
Issue number: #568
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.