fix(aws-lambda-python-alpha): poetry-plugin-export in build image #32761
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for this change
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. We solved the issue by using a custom build image that installs the plugin, I've added the Dockerfile in this PR.Description of changes
Installs needed plugin in build image
Description of how you validated changes
I use an image build from this Dockerfile in our deployments and it works
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license