Docs: Packages installed in the layer are different that the ones from aws_lambda_powertools[all]
#1942
Labels
documentation
Improvements or additions to documentation
Summary: Converting discussion into a doc issue so we can prioritize it in this iteration. We answered the discussion on why that is.
Discussed in #1807
Originally posted by ericbn January 4, 2023
Hi! 👋
Below is the list of installed packaged I get with a lambda using the
arn:aws:lambda:us-east-1:017000801446:layer:AWSLambdaPowertoolsPythonV2:17
layer, obtained with this code:Output:
And these are the packages I get by installing
aws_lambda_powertools[all,aws-sdk]==2.5.0
:Here's the difference (removed pip and setuptools from the left, which is the list from the layer):
Questions:
aws_lambda_powertools
extra(s)?aws_lambda_powertools[all]
(the "all" extra), or some other extra that is intended to match the packages in the layer?I'm assuming it's a good practice to add
aws_lambda_powertools[all]==2.5.0
to the dev dependencies and then deploy your lambdas only with extra dependencies beyond those already included as dev, because I was assuming those dev dependencies would be the exact same ones already provided in thearn:aws:lambda:us-east-1:017000801446:layer:AWSLambdaPowertoolsPythonV2:17
layer. In other words, I was expecting the diff above to perfectly match. I see it's not the case.(Side question: Any plans on updating the boto3 version in next releases of the layer and the package?)
The text was updated successfully, but these errors were encountered: