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

are there any examples for alternatives to a huge main func?   for creating a bunch of resources?  vpc + eks type things?

Yes, component resources 

<https://www.pulumi.com/docs/intro/concepts/resources/components/|https://www.pulumi.com/docs/intro/concepts/resources/components/>

thx much, i'll digest :slightly_smiling_face:

tho.. just scanning over it... how much should i reference other stacks?  for best practices?

Inside your components, never. Make the inputs for your component configurable and then do the stack reference in your main program 

ie, i lean towards creating a "core" stack, with VPC + EKS + few supporting things... logging buckets, cloud trail etc... and applications reference that stack... but would compartmentalizing it further be better?   Logging/sec/compliance things be best in their own stack, referencing a vpc stack?