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

One stack is one deployment, so while you could have many of them in the same C# project, you can not deploy them all at once.
You could have a configuration value, read it in main, and then pick a proper stack class, if that makes sense.

Yes makes perfect sense! Thanks for the clarification!

<@UB39JFCKC> could that be done with `pulumi up -c` or do you mean config outside of the usual pulumi config? I presume the latter since it would be read before the deployment run is called?

This could be done with command-line arguments to the dotnet executable when the automation api supports dotnet 

Also, given the automation api, you could presumably deploy multiple stacks from one dotnet project run by spinning up multiple automation “contexts”.

That’s a good point <@UCFNE2370>, our config won’t work outside a deployment.

Yes this is a perfect use case for Automation API. <@U018REFJ61K> come join us in <#C019YSXN04B|>. It's available in Go today. NodeJS is a work in progress and .NET and python will come right after.