Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for using Windows Subsystem Linux (WSL) SAM executable
See original GitHub issueIs your feature request related to a problem? Please describe.
PyCharm now supports using a WSL Python interpreter and WSL terminal. To complete the WSL development experience, I attempted to set the AWS Toolkit to use the SAM CLI executable from WSL under Settings -> Tools -> AWS -> SAM CLI executable: \\wsl$\Ubuntu-20.04\home\user\.local\bin\sam However, I am not able to save this configuration with the error: “Cannot Save Settings: Invalid sam executable: \wsl$\Ubuntu-20.04\home\user.local\bin\sam”
Describe the solution you’d like Support for using the SAM CLI executable in WSL for building, invoking locally, etc.
Describe alternatives you’ve considered The AWS Toolkit for VS Code in combination with Visual Studio Code Remote - WSL allows for using a SAM CLI executable in the remote development environment. I find the debugging tools and local Lambda invocation functionality to be much more mature in the AWS Toolkit for JetBrains and would prefer to use PyCharm over VS Code.
Additional context
Issue Analytics
- State:
- Created 3 years ago
- Reactions:19
- Comments:18 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1 I would love to see this get fixed.
Any news on this?