https://pulumi.com logo
Title
e

enough-painter-7423

01/26/2023, 5:37 PM
Hi, I'm an F# user, new to Pulumi. It seems like this issue is back? It was fixed by this PR but I can't seem to find out what the file updated by the PR looks like today, maybe the repo has been restructured Update: no, the GH issue was about sth called
Pulumi.Automation
, I'm not sure if it's still a thing today. But it was prob the same issue with mine in essence
$ dotnet paket why Grpc.AspNetCore 
Paket version 7.2.0+bb14ab674b2748070a624f394cd6796e11aaffa8
NuGet Grpc.AspNetCore - 2.51 is a transitive dependency.
It is part of following dependency chains:

-> Pulumi.Aws - 5.28
  -> Pulumi - 3.52.1
    -> Grpc.AspNetCore - 2.51

-> Pulumi.FSharp - 3.52.1
  -> Pulumi - 3.52.1
    -> Grpc.AspNetCore - 2.51
m

melodic-tomato-39005

01/26/2023, 5:47 PM
Hi @enough-painter-7423, the relevant csproj for Automation has moved here: https://github.com/pulumi/pulumi-dotnet/blob/main/sdk/Pulumi.Automation/Pulumi.Automation.csproj It seems that it does have the change, though. Looks like pulumi core has a dependency on AspNetCore. Maybe @echoing-dinner-19531 or @purple-potato-34526 can help out here?
e

echoing-dinner-19531

01/26/2023, 6:01 PM
Assuming this is only with paket, because pretty sure @purple-potato-34526 would of hit it for normal F# uses.
e

enough-painter-7423

01/26/2023, 6:03 PM
It does seem Paket-only, according my quick test with
pulumi preview
in
aws-fsharp
with and without Paket
I guess I should point out many (admittedly not all) F#ers use Paket... since Nuget until recenty left a lot to be desired wrt transitive pinning
Workaround:
Pulumi < 3.52
doesn't have the issue because
Grpc.AspNetCore
was added to
Pulumi
only 2 weeks ago
e

echoing-dinner-19531

01/26/2023, 6:51 PM
Oh I can see if I can fix that, probably just re-iterating the change from https://github.com/pulumi/pulumi/pull/6793 again
https://github.com/pulumi/pulumi-dotnet/pull/91 <- can probably get that merged and shipped today/tomorrow
e

enough-painter-7423

01/27/2023, 5:10 PM
Confirmed 3.53.0 fixed the issue. Thank you!