aws / aws/aws-toolkit-visual-studio
Have Publish to AWS Lambda use the profile in asw-lambda-tools-default
- Dominant language
- No language data
- Stars
- 135
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
In Visual Studio 15.9.14 the Publish to AWS Lambda defaults to the last used profile.
**Describe the solution you'd like**
I work with many clients and multiple AWS profiles. I cannot tell you the number of times a "Publish to AWS Lambda" has published to the wrong client.
The aws-lambda-tools-default.json contains the profile to use. Please default this to the profile when "Publish to AWS Lambda" is used.
Try opening Visual Studio on two projects (different client projects with different profiles). Switching between the two does not switch AWS profiles.
**Describe alternatives you've considered**
No easy workaround
**Additional context**
This is vital if you are working with multiple projects, multiple clients and multiple AWS profiles.
Contributor guide
Research direction
Start by tracing the Visual Studio “Publish to AWS Lambda” command and how it reads aws-lambda-tools-default.json. Reproduce the issue with two projects configured with different AWS profiles, then verify that switching projects selects each project’s configured profile when publishing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100