fix(lambda-python): handler path is incorrectly generated when using PythonFunction#20083
Conversation
TheRealAmazonKendra
left a comment
There was a problem hiding this comment.
Does this change have an issue associated with it? If so, please add it to the description.
We don’t have an open issue. |
TheRealAmazonKendra
left a comment
There was a problem hiding this comment.
Thank you for your contribution!
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
@Mergifyio refresh |
✅ Pull request refreshed |
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
When using PythonFunction, current implementation generates
handlervalue incorrectly.Code
Expected
Current Behaviour
This PR fix the issue by modifying string replace pattern.
All Submissions:
Adding new Unconventional Dependencies:
New Features
yarn integto deploy the infrastructure and generate the snapshot (i.e.yarn integwithout--dry-run)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license