(aws-lambda-python-alpha): The command "export" does not exist - Poetry

[sltmyr]

Describe the bug

Our python poetry lambda deployments started failing with the error message The command "export" does not exist. I guess this is due to the recent poetry 2.0 release (https://github.com/python-poetry/poetry/releases/tag/2.0.0) that removes the export command and relies on the poetry-plugin-export plugin instead. The issue can be solved by using a custom build image that installs the plugin, this is the Dockerfile that worked for me: https://github.com/aws/aws-cdk/pull/32761/files.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

No response

Expected Behavior

Lambda bundling succeeds.

Current Behavior

Bundling fails with The command "export" does not exist

Reproduction Steps

new lambda.PythonLayerVersion(this, "TestLayer", {
  entry: path.join(__dirname, "../layer"),
  description: "Test Lambda Layer with Poetry dependencies",
  compatibleRuntimes: [cdk.aws_lambda.Runtime.PYTHON_3_11],
});

Possible Solution

Install plugin in build image, see https://github.com/aws/aws-cdk/pull/32761/files

Additional Information/Context

No response

CDK CLI Version

2.142.1

Framework Version

No response

Node.js Version

18.0.0

OS

MacOS

Language

TypeScript

Language Version

No response

Other information

No response

[pahud]

Hi

I didn't get it. Where is the export command in your provided sample? Is it in the Dockerfile? If yes, can you share a minimal Dockerfile sample?

new lambda.PythonLayerVersion(this, "TestLayer", {
  entry: path.join(__dirname, "../layer"),
  description: "Test Lambda Layer with Poetry dependencies",
  compatibleRuntimes: [cdk.aws_lambda.Runtime.PYTHON_3_11],
});

And this sounds like an issue from poetry 2.0 and requires a plugin from poetry to work it around?

[igorsimko]

Hey @pahud, please check which version of aws-cdk you're using (not cli, but aws-cdk dependency in your project).

There was fix for installing correct version of poetry during lambda build in
95f8cef#diff-72edaa63ace26f9b6ba27bf4e9420a69f29a4fbe9e574e0c5a1ca269e5b5691a so you need at least version v2.93.0.

In my case I was using older version of aws-cdk where poetry version wasn't locked and with recent release of poetry (v2.0.0) bundling of lambda broke because it installed poetry version 2 where poetry export was dropped.

[sr-rossanderson]

I'm seeing similar issues in a couple of my AWS codepipelines now. I've not been able to find any way to pin the poetry version being used by the cdk synth command.

Also see this thread:

https://stackoverflow.com/questions/79335563/new-poetry-version-causing-issues-when-running-cdk-diff-due-to-the-aws-image/79338983#79338983

[pahud]

Thank you @igorsimko @sr-rossanderson. Looks like this issue is similar to #26823

Let me verify again.

[pahud]

Hi

Looks at this

aws-cdk/packages/@aws-cdk/aws-lambda-python-alpha/lib/Dockerfile

Line 9 in bbdd42c

ARG POETRY_VERSION=1.5.1

Looks like current POETRY_VERSION in the vended Dockerfile is 1.5.1. This means when you bundle your layer using the vended Dockerfile, 1.5.1 should be used, rather than 2.0 or above. Can you elaborate on why you are seeing this error?

I am using the 2.174.1 both CLI and lib.

 % npx cdk --version        
2.174.1 (build f353fc7)
hunhsieh@f84d898d8bae issue-triage % grep aws-cdk-lib package.json

    "aws-cdk-lib": "2.174.1",

[pahud]

@igorsimko

There was fix for installing correct version of poetry during lambda build in
95f8cef#diff-72edaa63ace26f9b6ba27bf4e9420a69f29a4fbe9e574e0c5a1ca269e5b5691a so you need at least version v2.93.0.

In my case I was using older version of aws-cdk where poetry version wasn't locked and with recent release of poetry (v2.0.0) bundling of lambda broke because it installed poetry version 2 where poetry export was dropped.

Yes the version pinning starts from 2.93.0 so you can't use 2.0 since then.