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

This may be better suited for the language specific channels <#CJ909TL6P|> probably would be the best bet 

<@U02R42MRL1G>, There are two constructs worth looking into:
• Component Resources: <https://www.pulumi.com/docs/intro/concepts/resources/#components>
• Stack References: <https://www.pulumi.com/docs/intro/concepts/stack/#stackreferences>
Component Resources allow you to create reusable classes that create one or more resources and then can be used across multiple projects/stacks. These can be referenced as local files or centrally stored as modules.
Stack References allow a stack to get data from a different stack. This page may also help: <https://www.pulumi.com/docs/guides/organizing-projects-stacks/>

<@U01BSQWRZFA> I think they were referencing doing something like this(Currently not working example) <https://github.com/M1kep/pulumi-learning/tree/main/github-typescript-with-oidc/src>

In the teams folders you have the team definitions, and in the repository folders you have the repository definitions. With traditional TF, there was no need to import or anything like that. But with TS, it’s a bit harder. Personally I’m also curious about whether or not there are any ways around this. I’m not hopeful though