Persisted and custom Lambda function requests

[martincostello]

I had a dig around in the Lambda Test Tool code and couldn't find an obvious way to get this working in the context of .NET Aspire.

I'd like to be able to provide a set of custom function requests that are always available to the tool/emulator:

As far as I could tell, no .lambda-test-tool directory has been created inside my solution.

What I'd like to do is have a directory in the solution root (to avoid the need to exclude it from publishing the project or needing to copy it to the build output) containing some custom requests, which I can then tell the Aspire integration to make available to the test tool.

[normj]

In the original version of the test tool we had the feature of saving events but in the original version the tool was run in the context of a project directory so the tool would know to store the events in the context of that directory.

In the new version of the test tool the tool is run out of process and potentially from any directory. What we could do is add an optional switch on the test tool to set a directory for persisting state like saved events. And then the Aspire integration can make that value configurable with a default somewhere relative from the app host.