Launching amazon.lambda.testtool-6.0 as debugger in RIDER fails to find any config files or Lambda methods in browser

[derekvantonder3DD]

Describe the bug

When launching amazon.lambda.testtool-6.0 as per the instructions in "Debugger configuration for Jetbrains RIDER", I'm not sure which directory to use for the working directory. The test tool launches a browser window, but I can't pick a lambda method or a config file. I've tried almost every directory in my project with no luck. What, exactly, is the testtool looking for in the working directory? A CF YAML template? Would love to have better documentation around this.

I have had success debugging with the following launchSettings.json, but I have to manually attach the debugger each time after the browser launches, which is frustrating:

"profiles": {
    "(macOS) Mock Lambda Test Tool": {
      "commandName": "Executable",
      "executablePath": "dotnet",
      "commandLineArgs": "lambda-test-tool-6.0 --port 5050",
      "environmentVariables": {
        "AWS_PROFILE": "XXXXXXXX",
        "AWS_REGION": "XXXXXXXX",
        "AWS_LAMBDA_RUNTIME_API" : "localhost:5050"
      }
    },

Expected Behavior

The amazon.lambda.testtool-6.0 debugger attaches automatically and finds the config/lambda methods.

Current Behavior

Exceptions are thrown and the debugger won't start.

Reproduction Steps

Don't have a clean repo to provide at this point, hoping for clarification on what the working directory should contain first.

Possible Solution

Documentation around what files exactly the test tool expects to find in the working directory when the debugger launches.

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

Amazon.Lambda.Core 2.2.0

Targeted .NET Platform

net6.0

Operating System and version

macOS

[ashishdhingra]

@derekvantonder3DD Good morning. Please follow instructions at Lambda Test tool: Configure for JetBrains Rider. It has one of the steps to Set the Working directory field to the .NET Core Lambda project root.

Thanks,
Ashish

[github-actions]

This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

[darthhiggy]

Hey, so, I'm having the same issue and I don't see a resolution. The link from the one comment is not helpful as that is the first thing I did. I set my project root and it has a config in there.

[eddiemcs3]

Re-opening the issue to follow-up @darthhiggy.

[darthhiggy]

So, I resolved the issue late yesterday. It had to do with the config. It was missing some key sections. I don't know what section I was missing originally but I found a copy of a working one and copied that. I didn't find much about the config file I'm the documentation but it might be there somewhere.

[eddiemcs3]

Thank you for the follow-up @darthhiggy. We'll follow-up to see what can be improved in the documentation so that it is clear.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

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.