fix(aws-lambda): use the correct camel case when accessing the SQS message attributes#4831
Open
dhruvparanjape wants to merge 2 commits into
Open
fix(aws-lambda): use the correct camel case when accessing the SQS message attributes#4831dhruvparanjape wants to merge 2 commits into
dhruvparanjape wants to merge 2 commits into
Conversation
dhruvparanjape
changed the title
Author
dhruvparanjape
force-pushed
the
fix_lambda_sqs_links
branch
from
July 21, 2026 19:37
ab1292e to
5842ef8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Use the correct camel case instead of the title case when accessing the SQS message attributes.
This is as per the aws docs https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#example-standard-queue-message-event as well as what I have observed when implementing the SQS links.
Fixes the implementation in #4668
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
uv run toxDoes This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.