Cannot target dotnet6 runtime for lambda's

Hello!

• Vote on this issue by adding a 👍 reaction
• To contribute a fix for this issue, leave a comment (and link to your pull request, if you’ve opened one already)

Issue details

In light of https://github.com/pulumi/pulumi-aws/issues/1837, where the option for dotnet6 was added to the NuGet package, I still cannot run pulumi up without errors.

Steps to reproduce

1. Create a Lambda.FunctionArgs where Runtime is set to Lambda.Runtime.Dotnet6. Note that I’m using the classic SDK (Pulumi.Aws on NuGet)
2. pulumi up

Expected: My deployment to run as dotnet6 was added. Actual: I got

Diagnostics:
  aws:lambda:Function (my-lambda):
    error: aws:lambda/function:Function resource 'my-lambda' has a problem: expected runtime to be one of [nodejs nodejs4.3 nodejs6.10 nodejs8.10 nodejs10.x nodejs12.x nodejs14.x java8 java8.al2 java11 python2.7
python3.6 python3.7 python3.8 python3.9 dotnetcore1.0 dotnetcore2.0 dotnetcore2.1 dotnetcore3.1 nodejs4.3-edge go1.x ruby2.5 ruby2.7 provided provided.al2], got dotnet6. Examine values at 'Function.Runtime'.

There also is a weird thing going on where pulumi plugin ls shows two resources:

NAME  KIND      VERSION  SIZE    INSTALLED     LAST USED
aws   resource  4.38.0   356 MB  14 hours ago  14 hours ago
aws   resource  4.37.5   355 MB  14 hours ago  14 hours ago

Even when I remove all resources, running pulumi up still downloads both resources. I’m not sure if this is expected behavior or relevant to the dotnet6 runtime problem.

[stack72]

Hi folks

I’ll have v4.38.1 published in the morning (UK time) to address this

Sorry for the problem here

Paul

[GodspeedYouBlackEmperor]

Hello, Looks like terraform-provider-aws in v. 4.4.0 is released already. It will be great to get at least an alpha package with the upgrade as soon as possible.