fix(aws-lambda-python): export poetry dependencies without hashes

[a-bigelow]

Export poetry dependencies without hashes to prevent bundling failures when a dependency provides a hash. Without this flag, users relying on the Poetry python dependency manager need to manually export their own requirements.txt file, as described in #14201

Fixes #19232

---

All Submissions:

• Have you followed the guidelines in our Contributing guide?

Adding new Unconventional Dependencies:

• This PR adds new unconventional dependencies following the process described here

New Features

• Have you added the new feature to an integration test?
  • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[gitpod-io]

[TheRealAmazonKendra]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

[a-bigelow]

Looks like tests are failing in a different module now. aws-lambda-python unit tests are passing on my end. As for integration tests, I will look and see if I can find a reason to update them -- integ.function.poetry is showing as UNCHANGED after packaging with the new poetry flag.

[a-bigelow]

Based on comments here, it seems like changes to assets are out of scope for the integration tests, so I would like to request an exemption on that front:

https://github.com/aws/aws-cdk/blob/main/packages/%40aws-cdk/aws-lambda-python/test/integ.function.poetry.ts#L44-L45

const integ = new IntegTest(app, 'poetry', {
  testCases: [testCase],
  // disabling update workflow because we don't want to include the assets in the snapshot
  // python bundling changes the asset hash pretty frequently
  stackUpdateWorkflow: false,
});

[a-bigelow]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[corymhall]

integ.function.poetry is showing as UNCHANGED after packaging with the new poetry flag.

Can you run the test with --force to force the test to run even though the snapshot doesn't have a diff?

yarn integ integ.function.poetry --force

✅ Updated pull request passes all PRLinter validations. Dissmissing previous PRLinter review.

Pull request has been modified.

[a-bigelow]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[a-bigelow]

My only lingering question here is whether --without-hashes should be default behavior. Evaluating hash integrity is itself an "opt-in" activity. Alternatively, I can refactor this to be based on a poetryIncludeHashes prop and flip the logic in Packaging.withPoetry()

[corymhall]

Thanks for updating the methods! I just have one minor nit.

Pull request has been modified.

[a-bigelow]

Changing default behavior to --without-hashes, per side discussion with Cory.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 8223c70
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).