I'm returning to this space after a break and then working on other things this year. I'd like to reboot everything to use c#/dotnet via the automation api. Quick questions: • Should I use 2.x or 3.0 beta (or even alpha)? • Is there a timeline for 3.0? (I need to be production ready in a couple of months) • I presume / hope it's much easier to debug stuff via the dotnet automation api? • Will I be able to exploit dotnet config sources to control config composition / overrides and pass it through to the automation api? • Has there been any progress on using dotnet to write dynamic providers? Really looking forward to it! 😀

Use 3.0, you are safe there

Yes on easier to debug. Yes you’ll be able to use any config source you want since you set Pulumi config values with automation api. Generic host and DI works with PulumiFn also.

@worried-city-86458 have you found anything on dynamic dotnet providers so far?

Subscribed thanks 👍

I don’t think we made much progress since then. @microscopic-pilot-97530 has the prototype.

Is it worth looking into implementing a resource plugin by implementing the grpc server in c#? I vaguely remember looking into that for terraform back in the day - they said you could technically write the plugin in any language but their terraform go plugin sdk did most of the lifting and you'd be on your own for a ton of stuff if you went without. same story here i'm guessing?