No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I could set the resources to have static names, but I'd rather use the dynamic ones so I don't run into collision issues

Assuming your SDK code is dependent on Pulumi code, you'll need to run it in an `Output.apply()` that's dependent on the resource that Pulumi creates. Or, you could use automation-api, that might make the structure a little easier to read.

Automation api is not available for dotnet/c#... yet

A dynamic provider might be the way to go, but those are also currently not supported for dotnet/c#

Yep, so the apply route might be best. But if you wanted to write a small nodejs or golang wrapper around your C# pulumi code... actually, might as well write two C# apps at the point, and call both from a script...