Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No module named 'lambda_function' #4562

Open
rejji opened this issue Mar 20, 2024 · 2 comments
Open

No module named 'lambda_function' #4562

rejji opened this issue Mar 20, 2024 · 2 comments
Labels
bug We can reproduce the issue and confirmed it is a bug. language:python Issues related to debugging Python lambdas using SAM Local needs-response Waiting on reply from issue/PR author. sam service:lambda

Comments

@rejji
Copy link

rejji commented Mar 20, 2024

Describe the bug
lambda_function is not locatable when executed from aws lambda console when locally things work fine.

To Reproduce

Expected behavior
Lambda should execute without giving this error: No module named 'lambda_function'

Screenshots

Attaching

Screenshot 2024-03-20 at 10 05 58 AM Screenshot 2024-03-20 at 9 52 43 AM Screenshot 2024-03-20 at 9 53 21 AM Screenshot 2024-03-20 at 9 55 30 AM Screenshot 2024-03-20 at 7 37 11 AM

StripeWebhookProcessor.tgz: Use this to open vcode and upload to lambda

Toolkit Logs
If applicable, attach toolkit logs by navigating to Extensions / AWS Toolkit / View Toolkit Logs: This navigation is not showing up.
I have checked the folder and adding following files from the folder ~/Library/Application Support/Code/logs/20240320T084750 for whatever executed today (20Mar). If something else is reqd let me know.

.//window3/exthost/amazonwebservices.aws-toolkit-vscode/aws_toolkit_20240320T084758.log
.//window2/exthost/amazonwebservices.aws-toolkit-vscode/aws_toolkit_20240320T084759.log
.//window1/exthost/amazonwebservices.aws-toolkit-vscode/aws_toolkit_20240320T084757.log

Development System (please complete the following information):

  • macOS Version:14.2 Beta (23C5047e)
  • Visual Studio Version: Version: 1.86.2 (Universal), Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda, V8: 11.8.172.18-electron.0, OS: Darwin x64 23.2.0
  • AWS Toolkit for Visual Studio Version: 2.15.0

Additional context
Following are few things I want to rectify wrt the files template.yaml, samconfig.toml using cli or click buttons rather than manually editing the file. How to do these?

  • I renamed the folder/project to StripeWebhookProcessor from StripeInBackend via VisualStudio. How to ensure this renaming is taken care in config files.
  • Name the function resource as StripeBackendFunction from existing HelloWorldFunction.
  • Update the CodeUri from hello_world/ to something meangingful like stripe_webhook/. (what does this mean?)
  • Update Events section to more meaningful word.
  • Also, I had put in three event files under events/ folder. After right-click-and-upload, these are not even visible in the AWS Lambda console. Over a period of attempts and checking, I had tried these few times and once the default event.json was observed to uploaded and visible at aws console.

Thanks

@rejji rejji added the bug We can reproduce the issue and confirmed it is a bug. label Mar 20, 2024
@awschristou
Copy link
Contributor

It looks like you are using the AWS Toolkit for VS Code, not the AWS Toolkit for Visual Studio. I will transfer this issue to the correct repo.

@awschristou awschristou transferred this issue from aws/aws-toolkit-visual-studio Mar 20, 2024
@justinmk3
Copy link
Contributor

HelloWorldFunction in your screenshots, maps to the name of the cloudformation "resource", it's unrelated to the hello_world folder name.

In the SAM template, Handler: lambda_function.lambda_handler means that Lambda will look for a python module (i.e. file) named lambda_function which contains a function named lambda_handler.

I renamed the folder/project to StripeWebhookProcessor from StripeInBackend via VisualStudio. How to ensure this renaming is taken care in config files.

Not possible currently.

Also, I had put in three event files under events/ folder. After right-click-and-upload, these are not even visible in the AWS Lambda console.

I believe the events/ folder is for sample payloads used by SAM CLI. The AWS Toolkit "Upload Lambda" doesn't do anything with that folder, currently.

@justinmk3 justinmk3 added needs-response Waiting on reply from issue/PR author. language:python Issues related to debugging Python lambdas using SAM Local service:lambda sam labels Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug. language:python Issues related to debugging Python lambdas using SAM Local needs-response Waiting on reply from issue/PR author. sam service:lambda
Projects
None yet
Development

No branches or pull requests

3 participants