LambdaTestTool-v2 support saved requests

[474D]

Describe the feature

Current Limitation The LambdaTestTool-v2 currently lacks the capability to persist requests -> "Save request" In contrast, the original .NET Mock Lambda Test Tool included this feature, which we actively used in our workflow.

I have looked into source code of LambdaTestTool-v2, it has capability of loading samples requests at the moment.

Proposed Solution

Enhance LambdaTestTool-v2 by introducing a 'Save request' feature, enabling the storage of sample requests for each function in individual files. These files can be included in the Git repository alongside the .NET Aspire setup. (this might require allowing to pass directory as a cmd arg or env variable to work well with .NET aspire setup).

As well it would be nice to: a) allow to hide standard sample requests if user has its own request samples b) filter request samples by function name if user has its own request samples (so if user selects function B, it only see's function B request examples)

Acknowledgements

• [x] I may be able to implement this feature request
• [ ] This feature might incur a breaking change

AWS .NET SDK and/or Package version used

Targeted .NET Platform

.NET 8

Operating System and version

Windows 11

[ashishdhingra]

Valid feature request. Needs review with the team.

[474D]

@ashishdhingra Awesome :) Will it be possible to know the outcome of the review once it has been completed?

I'm happy to raise a pull request (or multiple PRs) to implement either the full functionality discussed above or specific parts of it, depending on what’s preferred.

[philasmar]

We have added support for saving requests in the latest Test Tool release https://www.nuget.org/packages/Amazon.Lambda.TestTool/0.11.0. You will need to supply a path in the form of a command line argument to let the tool know where you want to save requests and settings https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool-v2#saving-lambda-requests.

[github-actions[bot]]

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.