Hi, when looking the source code I came across the lambda layer target. Will this be part of the 2.17 release, combined with the changes to the aws lambda layout?

huh…. well now i have a dumb question - if the point of Lambdex was to take all of the dependencies of your code and bundle them all up together, what would be the point of needing a layer?

build-time performance, I believe

ahhhhh okay, cool!

If you have deps that rarely change, rebuilding them all into the same pex can be laborious

makes sense. now my own hamster wheel is turning about our own lambda dependencies

Yes, this is the main benefit. Further, your lambda zip can only be 50MB unzipped. With layers you can increase the total to 250MB.

yeah my initial guess was going to be size-related

Yes, currently Docker provides the smoothes deployment. If I have the option to build layers somewhat easy I would prefer to move back to using a python runtime.

Categorisation of lambda changes: • 2.17: ◦ new layout available • 2.18: ◦ new layout is the default ◦

python_aws_lambda_layer

target ◦ function target renamed to

python_aws_lambda_function

◦ inferring a runtime from interpreter constraints, if unambiguous ◦ providing fixed complete platform JSONs for known runtimes • 2.19 (future) ◦ remove the old layout

@broad-processor-92400 Thanks for the information. I am really exited for

python_aws_lambda_layer

, this will make our deployment process a lot smoother. 2.18rc should be released in around 6 weeks? I do not want to upgrade to the dev version. I think this will be too big of a risk.

I don’t know the timeline for 2.18rc. I’d hope for sooner (as soon as 2.17 is out, but I don’t know where that is up to). If you’re in a position to test 2.18 (eg locally and/or in a dev environment, not in prod: I agree with your reticence to use a dev release day-to-day) and provide feedback/validate on the new Lambda functionality, that’d be appreciated. Currently the only experimentation/testing I’ve heard of so far is what I did while implementing and on my own work repo, so having others check it works smoothly early would be great!

Sure I will try it out. I already tried 2.17, works as expected. I will try out 2.18 in the coming days. Is there a open GitHub Issue to provide feedback?

Thank you! Not yet, but that’s a good idea. When I’m next at a computer, I’ll turn my summary message above into a discussion

@broad-processor-92400 is the `python_aws_lambda_layer`` activated in

2.18.0.dev6

? I get

Name 'python_aws_lambda_layer' is not defined.

Hmmm, that’s a surprise. I’ll look in a bit… thanks

@broad-processor-92400 It seems the

package

goal is not exported in

2.18.0.dev7

Edit: It seems like your PR was merged, but the goal still does not exist.

Yeah sorry, there’s another fix too, that isn’t in dev7: https://github.com/pantsbuild/pants/pull/19562 I think that’s finally there, though… 😅

Ok, perfect .I will try it out as soon as it is released.