refactor(typing): move more types into TYPE_CHECKING

[ericbn]

Issue number: #5029

Summary

Changes

Move more types into TYPE_CHECKING.

User experience

Following up issues reported in #5029.

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.

[ericbn]

Looking at the changes done as part of #4607, I double checked that this was the only place where we moved a pydantic import to outside TYPE_CHECKING. I see you already fixed this. I'm just trying to improve on top of your fix.

[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 SonarCloud

[leandrodamascena]

Hi @ericbn! Thanks for opening this PR! I'm planning to review it by Friday.

In the meantime, and if possible, can you please test version 3.0.0.dev10? I mean, maybe install it in some Lambda function and run your local tests or development environment? It would be great to get some feedback on this.

https://pypi.org/project/aws-lambda-powertools/3.0.0.dev10/

Thanks

[ericbn]

@leandrodamascena FYI these are the modules we use in our project:

• aws_lambda_powertools.event_handler: APIGatewayHttpResolver, Response
• aws_lambda_powertools.metrics: Metrics, MetricUnit, single_metric
• aws_lambda_powertools.shared.functions: strtobool
• aws_lambda_powertools.utilities.batch: BatchProcessor, EventType, process_partial_response
• aws_lambda_powertools.utilities.data_classes: APIGatewayProxyEvent, APIGatewayProxyEventV2, event_source
• aws_lambda_powertools.utilities.data_classes.sqs_event: SQSRecord (as type annotation for the code using the batch package)
• aws_lambda_powertools.utilities.parameters: get_parameter, get_parameters_by_name

I've updated our project to use plain aws-lambda-powertools==3.0.0.dev10 installed in our our shared layer, no other extras, nor any AWSLambdaPowertoolsPythonVX layer. Deployed it to a remote dev environment and all working like a charm!

[leandrodamascena]

@leandrodamascena FYI these are the modules we use in our project:

• aws_lambda_powertools.event_handler: APIGatewayHttpResolver, Response
• aws_lambda_powertools.metrics: Metrics, MetricUnit, single_metric
• aws_lambda_powertools.shared.functions: strtobool
• aws_lambda_powertools.utilities.batch: BatchProcessor, EventType, process_partial_response
• aws_lambda_powertools.utilities.data_classes: APIGatewayProxyEvent, APIGatewayProxyEventV2, event_source
• aws_lambda_powertools.utilities.data_classes.sqs_event: SQSRecord (as type annotation for the code using the batch package)
• aws_lambda_powertools.utilities.parameters: get_parameter, get_parameters_by_name

I've updated our project to use plain aws-lambda-powertools==3.0.0.dev10 installed in our our shared layer, no other extras, nor any AWSLambdaPowertoolsPythonVX layer. Deployed it to a remote dev environment and all working like a charm!

That's completely amazing to hear @ericbn! Thanks a lot for testing this! ❤️

[leandrodamascena]

Hi @ericbn! Sorry for the delay, but I had to travel for some internal meetings and I'm returning tomorrow and will finish this review this week.

Thanks

[leandrodamascena]

APPROVED! Thanks @ericbn! 🚀