Can't invoke a Lambda function that takes an int as a parameter with dotnet lambda invoke-function

[bjhogan]

Describe the bug

There doesn't seem to be a way to invoke a Lambda function using dotnet lambda invoke-function when the parameter to the function is an int.

Create a new Lambda function -

dotnet new lambda.EmptyFunction --name TakesANumber

Change the FunctionHandler to -

public string FunctionHandler(int input, ILambdaContext context)
{
    return $"you sent {input}";
}

Can't find a way to invoke this function using dotnet lambda invoke-function --payload ...

Have tried payloads with a variety of quotes, decimal places, etc.

Expected Behavior

Ability to invoke a function with a int payload.

Current Behavior

Cannot invoke function with an int payload.

Reproduction Steps

See description.

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

Amazon Lambda Tools for .NET Core applications (5.4.2)

Targeted .NET Platform

.NET 6

Operating System and version

Windows 10

[ashishdhingra]

Reproducible. Sending just 12 (for example) via AWS Lambda console works.

[ashishdhingra]

We need to implement fix similar to one in PR #1851.

EDIT: We copy .NET Extensions CLI tooling code in AWS Visual Studio Toolkit. VS Toolkit is targeting .NET Framework and hence it would not have System.Text.Json. So we should use the logic implemented in VS Toolkit, in .NET Extensions for CLI.

[ashishdhingra]

Fix released in Amazon.Lambda.Tools 5.11.1

[github-actions]

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.