You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the finding in aws-powertools/powertools-lambda-python#4111 we need to add the field to our model. The @types/aws-lambda does include it in their model but as undocumented field.
Why is this needed?
So we can parse and access DeadLetterQueueSourceArn when re-driving the messages from DLQ.
Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered:
am29d
added
triage
This item has not been triaged by a maintainer, please wait
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
labels
Apr 15, 2024
am29d
added
confirmed
The scope is clear, ready for implementation
parser
This item relates to the Parser Utility
and removed
triage
This item has not been triaged by a maintainer, please wait
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
labels
Apr 15, 2024
Summary
Based on the finding in aws-powertools/powertools-lambda-python#4111 we need to add the field to our model. The
@types/aws-lambda
does include it in their model but as undocumented field.Why is this needed?
So we can parse and access
DeadLetterQueueSourceArn
when re-driving the messages from DLQ.Which area does this relate to?
Parser
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: