Bug: getParameters
reports incorrect stack trace when transforms fails
#3950
Labels
bug
Something isn't working
confirmed
The scope is clear, ready for implementation
good-first-issue
Something that is suitable for those who want to start contributing
help-wanted
We would really appreciate some support from community for this one
parameters
This item relates to the Parameters Utility
Uh oh!
There was an error while loading. Please reload this page.
Expected Behavior
When receiving a
TransformParameterError
I should be able to see the correct stack trace that points me to where the error was thrown.Current Behavior
The error thrown when there's a transform error in the
getMultiple
code path is wrapping the originalTransformParameterError
error in another instance of itself, mangling the stack trace and making it harder to identify the issue.should be something like (notice the correct
transformValue
location):Code snippet
Steps to Reproduce
Example
Possible Solution
We should change this statement to just
throw error
.Powertools for AWS Lambda (TypeScript) version
latest
AWS Lambda function runtime
22.x
Packaging format used
npm
Execution logs
The text was updated successfully, but these errors were encountered: