[anishmehta24]

Issue number: closes #8712

Summary

Changes

SQSMessageAttribute.string_value and binary_value are typed str | None but indexed the dict directly. Lambda only includes the field matching the attribute's type (a String attribute has no binaryValue, a Binary one no stringValue), so reading the other one raised KeyError. Both now use self.get(...) and return None, which matches their type hints and the Pydantic SqsMsgAttributeModel; the docstrings say when the value is None.

Added test_sqs_message_attribute_with_only_one_value in tests/unit/data_classes/required_dependencies/test_sqs_event.py with a String and a Binary attribute shaped like the Lambda docs example; it fails on develop with KeyError: 'binaryValue'. The data classes and batch tests pass.

User experience

Before: record.message_attributes["text"].binary_value on a String attribute raises KeyError. After: it returns None.

---

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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[leandrodamascena]

Thanks @anishmehta24, confirmed with a real event: I sent a message with String, Number and Binary attributes through a queue to a function and Lambda delivers only the field matching the type, so binary_value on the String one raises KeyError on develop and returns None with your change, same as the Pydantic model already does.

I'm approving now. This goes out in 3.40.0, so it will sit here for a while before I merge it. No rebase needed in the meantime, and you'll be credited in the release notes.