This message was deleted.

Keep it all in a single "main" until you have an obvious reason to use multiple files/modules/classes.

thanks. this is existing infrastructure I'm working on importing in. This is not for a personal project, but will encompass quite a few resources. That said, I think I might have worked out a way forward, but am still tinkering

IaC is not as easily refactored as regular code because of the stateful nature (although it can definitely be refactored in Pulumi with aliases), so you're gonna want to keep it a little dumber than app code even if it does not read as pretty.

gotcha. I definitely need to have "global" things in one place, and "product" specific items elsewhere. One of the things I'm kicking around is how to reference something across multiple resources. For example, a single policy that needs assigned to several groups. The group requires the policy ARN. The major hurdle was I am attempting to create some generic methods and interface implementations, where method would basically just do a "execute the constructor for any class which implements IPolicy" as an example.

An IAM policy? Just create a managed policy and then attach it to multiple principals.

Advanced C# example with Automation API, it's nice to look at other dotnet examples https://github.com/gitfool/Pulumi.Dungeon