aws / aws/aws-toolkit-visual-studio
Allow selection of aws-lambda-tools-defaults file in the "Publish to AWS Lambda" panel
- 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.**
I use the "Publish to AWS Lambda" feature, I have multiple AWS profiles for each different environment and region.
Within the Lambda project I have multiple aws-lambda-tools-defaults files related to these profiles.
This can include the intended region and the S3 bucket that the build files will be sent to.
It loads the default as intended, but when I wish to deploy to any other environment and change the profile, information like the S3 bucket gets reset and doesn't pick up the alternate config file I have available.
**Describe the solution you'd like**
I would like to retain the use of the default file initially, but allow you to select an alternative configuration file within the same Lambda project, displayed via a dropdown list possibly, updating all relevant fields according to the selected configuration file.
**Describe alternatives you've considered**
One alternative could be to pick up the first matching configuration for the profile you selected, so if you select the test AWS profile, it will automatically select the aws-lambda-tools-defaults file that contains the "profile" : "test"
Another alternative is to open a file explorer to select the profile, allowing configurations outside that specific Lambda, but unless it starts in the same folder path as the default it would be harder to navigate.
**Additional context**
File structure showing the multiple configurations for Lambdas
Multiple AWS profiles in the AWS Lambda Deploy section
Example: default (dev AU)
Example: pretest UK
Contributor guide
Research direction
Start at the "Publish to AWS Lambda" panel and trace how it loads aws-lambda-tools-defaults and repopulates fields when the AWS profile changes. Inspect how configuration files are discovered within a Lambda project; done means an alternate file can be selected and its relevant values update the deployment fields while the default remains the initial choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100