feat(typing): add tenant_id property

[leandrodamascena]

Issue number: #6799

Summary

Changes

AWS Lambda RIC added a new field called tenant_id and we need to add this field to the context. This must be a string.

Also, I tested functions that already exists and new one and all of them are sending this context right now.

LambdaContext([aws_request_id=faf26568-ecb9-454b-a8f2-ff426c2fe22e,log_group_name=/aws/lambda/myfuncp13,log_stream_name=2025/06/12/[$LATEST]4c6c2d6baa594a008b5aeeea5017d6f4,function_name=myfuncp13,memory_limit_in_mb=128,function_version=$LATEST,invoked_function_arn=arn:aws:lambda:us-east-1:xxxxxx:function:myfuncp13,client_context=None,identity=CognitoIdentity([cognito_identity_id=None,cognito_identity_pool_id=None]),tenant_id=None])

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

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.

[dreamorosi]

Thanks for adding this, still need to test in Node.js.

Before merging, can you please add the key to this table?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.25%. Comparing base (9f20583) to head (2a3c118).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #6985   +/-   ##
========================================
  Coverage    96.25%   96.25%           
========================================
  Files          274      274           
  Lines        12856    12860    +4     
  Branches       950      950           
========================================
+ Hits         12374    12378    +4     
  Misses         377      377           
  Partials       105      105           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[leandrodamascena]

Thanks for adding this, still need to test in Node.js.

Before merging, can you please add the key to this table?

This is a good point, and I didn't intentionally change it. In Python, we don't dump the entire context to the log, but just add a few fields: https://github.com/aws-powertools/powertools-lambda-python/blob/develop/aws_lambda_powertools/logging/lambda_context.py#L37

To be honest, I'm not sure we should add tenant_id to the default log context. In cases where customers aren't using tenant_id, it will only cost money with an extra key and customers will have nothing to do with this key. I'd rather wait for customer feedback if they want this in the Lambda context in the logger.

I'd like to hear from you.

[dreamorosi]

Ok that makes sense, so this PR only adds it to the LambdaContext class/type but doesn't do any interaction with the Logger, is that correct?

If this is the case, do we want customers to know about it? Or have an easy way to use it with the Logger?

Right now if I'm using this feature in Lambda, as a customer using Logger I understand the only way I have is to do something like logger.append_key("tenant_id", context.tenant_id) (or equivalent), do we want to add a mention to the docs or show how to do something like we do with correlation ids?

[leandrodamascena]

Right now if I'm using this feature in Lambda, as a customer using Logger I understand the only way I have is to do something like logger.append_key("tenant_id", context.tenant_id) (or equivalent), do we want to add a mention to the docs or show how to do something like we do with correlation ids?

I think it makes sense. Let me work in this page to add all the fields customers can access when using LambdaContext object.

[dreamorosi]

Cool, I'm looking at notifications so feel free to re-request a review when you want me to check it.

[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

[dreamorosi]

Thank you for adding more info to the docs - let's go!