[Manishram-ai]

Issue number:
closes #8767

Summary

Changes

• SesReceiptAction.invocationType accepts RequestResponse as well as Event, and is optional. The SES docs list both values, and the captured event in Bug: SesSchema rejects documented SES receipt events powertools-lambda-typescript#5771 doesn't have it.
• Every field in SesMailCommonHeaders is optional now. SES only sends the headers the email has, so an email sent only to BCC recipients has no to.
• In the SESEvent data class, to and get_from return [] when the header is missing, like cc and bcc already do. return_path, date, message_id, subject and invocation_type return None instead of raising KeyError, so their return types change from str to str | None.
• New tests cover both invocation types, a missing invocation type and an email with no common headers, for the parser model and the data class.

This is the same fix as aws-powertools/powertools-lambda-typescript#5772. The replyTo part of that PR was already done here in #8525.

User experience

Today, events from a Lambda action invoked with RequestResponse, and emails without a To or Subject header, fail with a ValidationError in the parser and a KeyError in the data class. With this change they parse, and the missing headers come back as None (or [] for the list headers in the data class).

Verification

• 4 of the 5 new tests fail on develop and pass with this change. The Event case already passed.
• tests/unit/parser and tests/unit/data_classes/required_dependencies: 366 passed (Python 3.12).
• ruff check, ruff format --check and mypy are clean on the changed files.
• I didn't run this against a live SES receipt rule. The field rules come from the SES docs, and the missing invocationType comes from the captured event in the TypeScript issue.

---

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