awslabs / awslabs/amazonq.nvim
Add native TLS support for corporate environments in WSL
- Dominant language
- Lua
- Stars
- 188
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Currently using neovim (lazyvim) within wsl on company machine. This plugin works for the free tier start link, but not the organisation pro url which I believe is due to TLS requirements. It works fine within vscode. For other tools, such as uv, I have to specify --native-tls to get pass this.
Would be nice if this plugin could specify this, or have better documentation around authentication.
Currently getting this error when calling login:
Amazon Q: {
code = -32603,
message = "Request workspace/executeCommand failed with message: UnknownError"
}
Thanks :)
Contributor guide
Research direction
Start by reproducing the login failure for the organisation pro URL in Neovim on WSL, then compare it with the working VS Code and uv native-TLS behavior. The issue is complete when native TLS support works for that login or the authentication and TLS configuration is documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, neovim
- Domain
- authentication, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100